husky

I've found that keeping my CLAUDE.md minimal (under 100 lines) yields the best results. I focus mainly on these areas: - Essential project context and purpose - A minimal project structure to help locate types, interfaces, and helpers - Common commands to avoid parsing package.json repeatedly. Regarding the specific practices mentioned: Implementation Flow: I've noticed Claude Code often tries to write all tests at once, then implements everything when import fails (not true TDD). To address this, I created a TDD-Guard hook that enforces one test at a time, test fail for the right reason, only implement the minimal code to make the test pass. Code quality: I've had good success automating these with husky, lint-staged, and commitlint. This gives deterministic results and frees up the context for more important information. When Stuck: I a

husky (git hooks) https://github.com/typicode/husky

Black is an interesting example because you want two different commands in your pre-commit versus CI/CD, at least in my estimation. In pre-commit you want to run Black in full formatter mode on the staged files. (VS Code's "Format After Save" does most of the work already, but every now and then it slips on something.) In CI/CD you want the check that formatting occurred and block it as a failed test. Those are different commands. For what it is worth, I was evaluating lint-staged [1] and husky [2] for my pre-commit hooks. [1] https://github.com/okonet/lint-staged [2] https://github.com/typicode/husky

In JavaScript projects we're using Husky [1]. I'm sure other environments have their own equivalents of it. [1] https://github.com/typicode/husky

You could use something like https://github.com/typicode/husky to prevent a push if the linter fails.

That's interesting, I didn't know about this issue. There are a couple of solutions in this GitHub issue FYI: https://github.com/typicode/husky/issues/108

The best way to introduce a formatter is with a git hook on commit/push (for JS projects see Husky), to ensure everyone is onboard and avoid exactly the formatting churn you mention. Thanks LaurensBER for the ‘git blame’ solution! https://github.com/typicode/husky

This is similar to the Conventional Changelog: https://github.com/conventional-changelog/conventional-chang... I often use a customized Commit Lint in combo with Husky to enforce conventional changelog messages: https://github.com/marionebl/commitlint https://github.com/typicode/husky You can also throw in something like the Commitizen cli for newcomers: https://github.com/commitizen/cz-cli

For JS projects, I recommend husky: https://github.com/typicode/husky

On the other hand, if you are using `TODO` comments within your code, a good idea is to place something like the `fixme` CLI [0] into a prepush hook [1] so that it is always highly visible. The length of this output then acts as an intuitive measure of accrued technical debt and can be leveraged within a team to get time to fix the underlying problems. [0] https://github.com/JohnPostlethwait/fixme [1] https://github.com/typicode/husky