Git Commit Rules

SkillDev tools

Git Commit Rules

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Git Commit Rules skill

What this skill tells your AI

The instructions your AI receives, as published by vibeeval/vibecosystem in skills/git-commits/SKILL.md and read by ahel’s review.

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>

Signals

GitHub stars
530
Forks
44
Last commit
Aug 2026

ahel recommends instead

Advanced
Catalog kind
skill
Gateway key
git-commits-vibeeval
Source
github.com/vibeeval/vibecosystem