Git Commit Rules
When the user asks to commit, push, or save changes to git:
MUST Use /commit Skill
DO NOT run git commit directly. Instead:
code
Skill("commit")
The /commit skill:
- •Removes Claude attribution from commits
- •Generates reasoning.md capturing what was tried
- •Clears build attempts for next feature
Why This Matters
- •Regular
git commitadds "Generated with Claude Code" and Co-Author lines - •The
/commitskill removes these so commits appear user-authored - •Reasoning capture preserves build history for future sessions
Trigger Words
When you see these in user prompts, use the commit skill:
- •"commit", "push", "save changes"
- •"push to github", "push changes"
- •"commit and push"
After Commit
The skill will prompt you to run:
bash
bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <hash> "<message>"
Then push if requested:
bash
git push origin <branch>