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 /maestro: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 Maestro" and Co-Author lines
• The /maestro: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 .maestro/scripts/generate-reasoning.sh <hash> "<message>"

Then push if requested:

git push origin <branch>