Git commits
Skill ulpi-io/plugin-marketplace/plugins/parcadei/skills/git-commits
A curated collection of 7,800+ agent skills for Claude Desktop, sourced from skills.sh
npx -y skills add ulpi-io/plugin-marketplace --skill git-commitsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Git Commit Rules
SKILL.md
1.0 KB, 232 tokens by cl100k_base, as published. Nobody here has run it
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>