<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pre-Commit on Advancing Engineering</title><link>https://www.advancingengineering.dev/tags/pre-commit/</link><description>Recent content in Pre-Commit on Advancing Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 06 May 2026 11:14:47 +0100</lastBuildDate><atom:link href="https://www.advancingengineering.dev/tags/pre-commit/index.xml" rel="self" type="application/rss+xml"/><item><title>Pre-commit Hooks: Enforcing Quality at the Source</title><link>https://www.advancingengineering.dev/posts/2026-04-pre-commit-hooks/</link><pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.advancingengineering.dev/posts/2026-04-pre-commit-hooks/</guid><description>&lt;p&gt;Pre-commit hooks catch issues before they reach CI — shifting quality checks as far left as possible.&lt;/p&gt;
&lt;p&gt;In an AI-assisted workflow this matters more than ever. LLM-generated commits are faster and more numerous; human review bandwidth is the same. Pre-commit hooks are how you define &amp;ldquo;done&amp;rdquo; in a form the machine can check — and the LLM can iterate on.&lt;/p&gt;</description></item></channel></rss>