More testing is better, so far! I'm using the same red-green-refactor TDD idea, and having Claude use Superpowers code review and running Coderabbit CLI on it all before pushing to CI/CD, which also runs a series of tests (mostly security ones). Someone else posted that whenever something broke they would ask 'Why was it built that way?' to try to have the bot fix it's own coding patterns.. as well as adding a regression test to ensure it did not happen again. I also have it do dry-runs and then do live on one item before batching. Catches a lot of things! Oh, and insist that it RTFM's the API if you're using one.