<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Prek on Advancing Engineering</title><link>https://www.advancingengineering.dev/tags/prek/</link><description>Recent content in Prek on Advancing Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 09 Aug 2026 17:20:15 +0100</lastBuildDate><atom:link href="https://www.advancingengineering.dev/tags/prek/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 problems before they reach CI: bad formatting, broken builds, leaked secrets. All of it, in under a second, before you&amp;rsquo;ve even pushed.&lt;/p&gt;
&lt;p&gt;I recently checked across my team. Ninety-five percent had no pre-commit hooks set up. Not because anyone disagreed with the idea — few made it a five-minute priority, so it stayed undone.&lt;/p&gt;
&lt;p&gt;Here&amp;rsquo;s the five minutes.&lt;/p&gt;</description></item></channel></rss>