<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Husky on Commentary of Takao</title><link>https://takao.blog/en/tags/husky/</link><description>Recent content in Husky on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/husky/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating Pre-Commit Checks with Husky and Git Hooks</title><link>https://takao.blog/en/web/git-hooks-husky-prevent-bugs/</link><pubDate>Sun, 20 Apr 2025 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/git-hooks-husky-prevent-bugs/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post Automating Pre-Commit Checks with Husky and Git Hooks" /&gt;&lt;h2 id="introduction"&gt;Introduction
&lt;/h2&gt;&lt;p&gt;In team development, simple mistakes like committing code with syntax errors or bad formatting are common. These issues can break the CI build or lead to messy formatting wars during code reviews.&lt;/p&gt;
&lt;p&gt;Instead of relying on developer vigilance to enforce guidelines, you can automate these checks.&lt;/p&gt;
&lt;p&gt;By combining &lt;strong&gt;Git Hooks&lt;/strong&gt; with &lt;strong&gt;Husky&lt;/strong&gt;, you can automatically trigger linters (ESLint), formatters (Prettier), and unit tests (Jest) before any commit or push is finalized. This guide walks you through setting up this workflow.&lt;/p&gt;</description></item></channel></rss>