Nizoss

5 ms·

1.
by Nizoss 3mo ago
I use a different approach, I enforce TDD using hooks. Think of it this way: You interact with your agent and ask it to implement a feature. Now every change it wants to make will have to be approved by a separate agent. This second agent i
2.
by Nizoss 4mo ago
Good resource and nicely organized. I took the opportunity to apply a couple new things.
3.
by Nizoss 4mo ago
I’m working on a project that blocks agents from breaking rules. The rules are enforced through hooks and work across Claude Code, Codex, and GitHub Copilot. https://github.com/nizos/probity
4.
by Nizoss 4mo ago
Exactly! I have said this a couple of times but it was taken literally as in no capital letters or strong language. Glad to see someone else who shares this perspective.
5.
by Nizoss 4mo ago
Not throwing shade at anyone here but the thought has definitely crossed my mind that we are recreating SAFe but for agents when looking at some of the orchestration setups out there. I think that it is better to not force the same hierarch
6.
by Nizoss 4mo ago
I fully agree. Also started using husky before expanding further and created my own hooks. I can’t imagine myself using agents today without them, it would require a lot of babysitting.
7.
by Nizoss 4mo ago
Sounds interesting, can you elaborate on your thinking? Got me curious.
8.
by Nizoss 4mo ago
Exactly! I don’t babysit TDD anymore. I have another agent that does that for me and honestly sometimes catches things I would have missed if I was the babysitting. Hooks do wonders here. The payload contains a lot of information about the
9.
by Nizoss 4mo ago
If you’re interested in such deterministic scaffolding/control flow, check out Probity. I created it to address this exact issue. It is a vendor-neutral ESLint-style policy engine and currently supports Claude Code, Codex, and Copilot.
10.
by Nizoss 5mo ago
Creator of TDD Guard here, thanks for the mention! TDD Guard was built when Claude Code was the only one to offer hooks. Plugins didn't exist and the models were weaker, so the validation context and instructions took more work to get
11.
by Nizoss 9mo ago
This is how I would also love to work but not all teams prefer this way. How many are you in your team? Was it easy to switch?
12.
by Nizoss 9mo ago
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
13.
by Nizoss 9mo ago
Yes! This is something that I also value. Having demo gifs of before and after helps a lot. I have encountered situations where what I thought was a minor finishing clean up had an effect that I didn't anticipate. By including demos in
14.
by Nizoss 9mo ago
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,
15.
by Nizoss 10mo ago
This looks really useful! Great work!
16.
by Nizoss 1y ago
If you're on Windows and using vscode, add thiss to keybinds.json [ { "key": "shift+enter", "command": "workbench.action.terminal.sendSequence", "args": {
17.
by Nizoss 1y ago
And here I am still waiting for some kind of hooks support for ChatGPT/Codex.
18.
by Nizoss 1y ago
Same issue here, dark mode on mobile.
19.
by Nizoss 1y ago
Yeah, this is a no brainer for certain use cases.
20.
by Nizoss 1y ago
Not that I'm aware of. I'll check what possibilities exist with Opencode on their Discord.
21.
by Nizoss 1y ago
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/sr
22.
by Nizoss 1y ago
Thanks for the TL;DR! Go support was recently added, and TDD-Guard also works with these frameworks: JavaScript/TypeScript: Vitest and Jest Python: Pytest PHP: PHPUnit Go: Native go test Adding a new language or framework just means cr
23.
by Nizoss 1y ago
Hi HN, I believe that using guardrails with agentic coding is far more effective than simply using instructions. This plugin demonstrates it using Test-Driven Development. TDD-Guard can now be used with Go. Other supported languages are: JS
24.
Show HN: TDD-Guard – Test-Driven Development for Claude Code(github.com)
4 points by Nizoss 1y ago|7 comments
25.
by Nizoss 1y ago
I'm genuinely curious to see what the software quality looks like with this approach. Particularly how it handles complexity as systems grow. Feature development is one thing, going about it in a clean and maintainable way is another.
26.
by Nizoss 1y ago
Same, I manually approve and steer each operation. I don't see how cleaning up and simplifying after the fact is easier or faster.
27.
by Nizoss 1y ago
It's a tough position to be in. I feel that I finally have some expertise worth sharing but at the same time I want to avoid backlash from the community for promoting my own content and projects. At the same time, I really do enjoy rea
28.
by Nizoss 1y ago
I fail to see how this addresses the issue of poor quality contributions or bloat. I feel that focusing on the real issue would be more productive.
29.
by Nizoss 1y ago
I also use the default one by Anthropic. It's a good start and simple enough to adjust for any needa.
30.
by Nizoss 1y ago
Hi HN, I have been using Claude Code in production for a couple of months and noticed most content and discussions focus on either flashy demos or complex orchestrations. This is what I found works best for me and how I actually ship code.

More ›