Menu
Git Commit Rules
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Maestro spec-driven development for Claude Code. Load this skill when invoking Maestro commands so workflows stay aligned with LeIndex and the Rust TUI.
Maestro spec-driven development for Gemini CLI. Load this skill when invoking Maestro commands so workflows stay aligned with LeIndex and the Rust TUI.
Maestro spec-driven development for Amp CLI. Load this skill when invoking Maestro commands so workflows stay aligned with LeIndex and the Rust TUI.
Show users how Maestro works - the opinionated setup with hooks, memory, and coordination
Full 5-layer analysis of a specific function for debugging or deep understanding
Get a token-efficient overview of any project using the TLDR stack
| name | git-commits |
| description | Git Commit Rules |
| user-invocable | false |
When the user asks to commit, push, or save changes to git:
DO NOT run git commit directly. Instead:
Skill("commit")
The /maestro:commit skill:
git commit adds "Generated with Maestro" and Co-Author lines/maestro:commit skill removes these so commits appear user-authoredWhen you see these in user prompts, use the commit skill:
The skill will prompt you to run:
bash .maestro/scripts/generate-reasoning.sh <hash> "<message>"
Then push if requested:
git push origin <branch>