tdd-guard

If you’re just looking for the TDD part - https://github.com/nizos/tdd-guard - is the only project I’ve come across that actually enforces it with hooks and blocks edits rather than relying on a prompt that gets context rotted away.

I would love to hear your thoughts on TDD-Guard. An open source plugin I created to enfore Test-Driven Development practices on agents: https://github.com/nizos/tdd-guard

If you write your tests the Test-Driven Development way in that they first fail before production changes are introduced, you will be able to trust them a lot more. Especially if they are well-written tests that test behavior or contracts, not implementation details. I find that dependency injection helps a lot with this. I try to avoid mocking and complex dependencies as much as possible. This also allows me to easily refactor the code without having to worry about breaking anything if all the tests still pass. When it comes to agentic coding. I created an open source tool that enforces those practices. The agent gets blocked by a hook if it tries to do anything that violates those principles. I think it helps a lot if I may say so myself. https://github.com/nizos/tdd-guard Edit: I realize now that I misunderstood your comment. I was qui

That sounds amazing! Thanks for the heads up! I deliberately picked a vendor-agnostic name. Adding support for other clients mainly means extending IClient: https://github.com/nizos/tdd-guard/blob/main/src%2Fcontracts... https://github.com/nizos/tdd-guard/tree/main/src%2Fvalidatio... I'll take a closer look into adding this support. I'd also welcome a contribution if that's something you would be interested in! The question is, do other agent platforms support hooks or similar functionality?

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

I have been using Claude Code with TDD through hooks, which significantly improved my workflow for production code. Watching the ChatGPT 5 demo yesterday, I noticed most of the code seemed oriented towards one-off scripts rather than maintainable codebases which limits its value for me. Does anyone know if ChatGPT 5 or Copilot have similar extensibility to enforce practices like TDD? For context on the approach: https://github.com/nizos/tdd-guard I use pre/post operation commands to enforce TDD rules.