Git Commit Rules
Install
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill git-commitsSKILL.md
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:
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 "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <hash> "<message>"
Then push if requested:
git push origin <branch>
Related skills
setup-matt-pocock-skillsmattpocock905KConfigure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.hyperframes-cliheygen-com714KUse the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, timeline, history, docs, benchmark, telemetry, transcribe, auth, tts, and remove-background. Also use when diagnosing build or render failures. validate, inspect, and layout are deprecated aliases; use check. Covers loimplementmattpocock627KImplement a piece of work based on a spec or set of tickets.ask-mattmattpocock626KAsk which skill or flow fits your situation. A router over the skills in this repo.
