git-commits

Solid

Git Commit Rules

Code & Development 496 stars 41 forks Updated 1 months ago MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
90
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
49
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <hash> "<message>" ``` Then push if requested: ```bash git push origin <branch> ```

Details

Author
vibeeval
Repository
vibeeval/vibecosystem
Created
2 months ago
Last Updated
1 months ago
Language
C#
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category