smithery.ai

git-commits

Git Commit Rules

First seen Mar 8, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,025 B
  • docs SUMMARY.md 35 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 24 installs

SKILL.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:

  1. Removes Claude attribution from commits
  2. Generates reasoning.md capturing what was tried
  3. 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>