make tdd-guard less strict

[tfriedel]

I observed that Claude Code wanted to write little debug scripts to reproduce an issue. These temporary scripts would not be part of the main project and get deleted later.
I think it's a valid reason.
There may be more reasons.
I'm not sure yet what the best approach would be, maybe have a way to modify the rules for tdd-guard?

I often miss such things unless I observe what claude's doing. Maybe it would be also good to ask if it could ask for me to disable tdd-guard for certain tasks like debug scripts or refactoring? It's not ideal cause tbh I like running in YOLO mode where I'm not getting asked at all.

[VilemP]

It tries to do that for me too. But I actually hate it. I think that is not the right way to figure out how your code actually works. I think it is signalling a lack of tests that would tell you. So I would rather like CC to write more tests to understand how it works and where the problem is. This way, I also prevent any regression.

[nizos]

Hi @tfriedel,

Thanks for reaching out! I completely understand your use case.

We are looking into revising the instructions and to also make it possible to customize TDD instructions or set different strictness levels. There is a discussion started by @VilemP here where we are gathering input: #44

In the meantime, you can use the following strategies:

• use quick commands to toggle on/off tdd-guard as needed
• use custom ignore patterns to control which files/paths are validated.

Using the custom ignore patterns, you can allow it to create changes/scripts in certain directories to replicate issues, for example temp/. You can add an instruction to CLAUDE.md that it can use that directory for temporary scripts if it suits you.

I hope that these workarounds would provide you with enough flexibility until the next batch of improvements are ready. Feel free to share any other scenarios where you need more flexibility! :)

[nizos]

I have proposed a solution here, would love to hear your thoughts on it:
#44 (comment)

[nizos]

It should now be possible to customize TDD validation rules in the latest version: 0.10.0.
Thanks again for all the ideas and feedback!