mcpbeat

Git Commits

parcadei/git-commits

Git Commit Rules

256 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3880
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill git-commits

The instruction itself

5 sections, as written by the author

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 commit adds "Generated with Claude Code" and Co-Author lines
  • The /commit skill 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>

How to use it

Copy the folder

Take parcadei/git-commits from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.