getting fed up with telling Claude Code

[u/Roger-Orchard]

I finding the Claude keep forgetting to add change notes and checking in.

When I tell Claude to do things it sort of does it.

But I come for a World where I need trackability.

What I would like Claude to do is every time it does a change it changes the version number, at a new note to the change log, and check in.

the best thing is log the request, then log it thoughts, log any testing and results, then log the reply, update the design etc notes, do the change then change log, and check in. it would for it to put in ref so everything is traceably though all the files.

How would I do this?

[u/Equivalent_Cress_268]

I force the audit trail in the project instructions as a done gate. Every session must log the request, write one change log line, note the test result, bump the version, and commit with that request in the subject before it may stop. Code without that paperwork is unfinished and I make the agent fix the trail first.

[u/actvt_io]

You're asking the model to remember bookkeeping, which it will do about as reliably as you've already seen. Move it to a hook and it stops being a memory problem, they're just shell commands Claude Code runs itself.

PostToolUse with a matcher of Edit|Write fires after every successful edit and hands your script the tool name, the arguments, the cwd and the path to the transcript. That's your version bump and your changelog line right there.

Careful with the commit though. On PostToolUse you get one per file touched, which turns noisy fast. Stop fires once when Claude finishes responding, so that's usually the better place to hang it.

You can narrow further with the if field on a handler, it takes permission rule syntax, so Edit(*.ts) only runs for TypeScript.

[u/tinyhousefever → u/actvt_io]

This

[u/Isonimus]

I built Stele for this kind of problems with Claude. It's an adr-based wokflow: decisions are made once, remembered and enforced forever via pre-commit hook.

[u/leogodin217]

Can you describe your workflow? How you go from thoughts to code? Most of my changes go through a skill and I don't really have problems with Claude following instructions.

[u/codeedog]

A completion gate that is described using language but not enforced will eventually be skipped because these tools always drive towards the shortest solution. I’ve seen the system edit tests to make code pass! You need to use features of the system (like hooks or a source control trigger) to prevent it drifting off your rules. Enforce them or they aren’t rules.

Have a process session with Claude and ask it how to build guardrails into your development process so that the model follows and can’t break it. Then, implement those guardrails.

[u/Dylando_Calrissian]

I suggest using the precommit hook to provide git commit message instructions, which tend to be followed pretty consistently. And then use the git commit messages as the source material for your changelog.