Is there a way to automatically run tests every file change, like post tool somehow, so that it returns a concise test run back to the LLM every tool use? That seems like it would be useful.

▲

rane 5 hours ago | parent | next [-]

You don't want to run tests after every file change, because that will distract Claude from finishing whatever it's doing and add noise to the context window. Of course the tests will be broken if Claude hasn't finished the full change yet.

Running tests makes most sense on the Stop hook event, but personally I've found CLAUDE.md instruction of "Run `just check` after changes" to be effective enough. The Stop hook has the issue that it will run the checks every time Claude stops responding, even after without any changes.

	▲	odie5533 5 hours ago \| parent [-]
		Won't the LSP distract Claude too? I am trying to think of ways to make Claude faster at iterating by reducing tool calls. That always seems to be a bottleneck when it's doing tons of back-and-forth with tool calls.

▲

spellboots 7 hours ago | parent | prev [-]

Yes, you can do this with hooks: https://code.claude.com/docs/en/hooks

	▲	kristianp 6 hours ago \| parent [-]
		Back when I was using CC, I had a "mandatory" development workflow that checks if the corresponding test file exists for the changed file, runs tests and runs the test coverage tool for the changed file.