Thanks, that sounds all very reasonable!

> Basically, reviewing output from Claude (or Codex, or any model) that hasn't been through multiple automated review passes by a model first is a waste of time - it's like reviewing the first draft from a slightly sloppy and overly self-confident developer who hasn't bothered checking if their own work even compiles first.

Well, that's what the CI is for. :)

In any case, it seems like a good idea to also feed the output of compiler errors and warnings and the linter back to your coding agent.

> Well, that's what the CI is for. :)

Sure, but I'd prefer to catch it before that, not least because it's a simpler feedback loop to ensure Claude fixes its own messes.

> In any case, it seems like a good idea to also feed the output of compiler errors and warnings and the linter back to your coding agent.

Claude seems to "love" to use linters and error messages if it's given the chance and/or the project structure hints at an ecosystem where certain tools are usually available. But just e.g. listing by name a set of commands it can use to check things in CLAUDE.md will often be enough to have it run it aggressively.

If not enough, you can use hooks to either force it, or sternly remind it after every file edit, or e.g. before it attempts to git commit.