Not sure re the contribution policy or the project philosophy around this kind of thing (e.g. how to know if its actually helping?) but I'd be happy to make PR or write up a more detailed set of considerations if that would be welcomed. Thanks again for a dope template!
Anecdotal Failure to Commit
CLAUDE.md currently reads:
- **Commit after each user request**: When completing what the user asked for, immediately commit: `git add -A && git commit -m "[action]: [what was accomplished]"`
- Commits should happen WITHOUT asking - they're for checkpoints, not cleanliness (will be squashed later)
Problem
In my hands (and as reported by my co-founder) claude semi-regularly fails to commit between features / turns as instructed. Finger to the wind, maybe once every 30min-2 hours of continuous use? (10+ failures to commit observed probably).
This is usually fine (I usually remind claude to review the CLAUDE.md, or commit manually) but in two instances this caused hours of wasted time as claude combined key improvements and absolute insane nonsense without committing in between.
Fix idea: Commit reminder (claude hook)
Claude Code hooks are user-defined shell commands that execute at various points in Claude Code’s lifecycle. Hooks provide deterministic control over Claude Code’s behavior, ensuring certain actions always happen rather than relying on the LLM to choose to run them.
Quickstart
Reference
A hook could check if there are uncommitted files with git status and if so send a message like "Automatic reminder (uncommitted work) CLAUDE.md has guidance for git usage".
This message would aim to keep CLAUDE.md source of truth on git usage, and is the smallest diff from the current behavior (autocommitting would be a bigger jump). UserPromptSubmit seems like the simplest hook event option rn.
Not sure re the contribution policy or the project philosophy around this kind of thing (e.g. how to know if its actually helping?) but I'd be happy to make PR or write up a more detailed set of considerations if that would be welcomed. Thanks again for a dope template!
Anecdotal Failure to Commit
CLAUDE.md currently reads:
Problem
In my hands (and as reported by my co-founder) claude semi-regularly fails to commit between features / turns as instructed. Finger to the wind, maybe once every 30min-2 hours of continuous use? (10+ failures to commit observed probably).
This is usually fine (I usually remind claude to review the CLAUDE.md, or commit manually) but in two instances this caused hours of wasted time as claude combined key improvements and absolute insane nonsense without committing in between.
Fix idea: Commit reminder (claude hook)
A hook could check if there are uncommitted files with
git statusand if so send a message like "Automatic reminder (uncommitted work) CLAUDE.md has guidance for git usage".This message would aim to keep CLAUDE.md source of truth on git usage, and is the smallest diff from the current behavior (autocommitting would be a bigger jump).
UserPromptSubmitseems like the simplest hook event option rn.