// Use when the user asks to commit changes, stage and commit, or says "commit my changes" — stages all uncommitted changes and creates a structured commit message with emoji, title, and summary
| name | git-commit |
| description | Use when the user asks to commit changes, stage and commit, or says "commit my changes" — stages all uncommitted changes and creates a structured commit message with emoji, title, and summary |
Stages and commits all uncommitted changes with a structured message: a random emoji, a concise title, and a short summary. Optionally adds a Co-Authored-By line if the user mentions agent helped.
Permissions required: git commit, git rebase
[emoji] [title]
[summary — 1 to 5 lines depending on complexity]
With co-authorship:
[emoji] [title]
[summary — 1 to 5 lines depending on complexity]
Co-Authored-By: [model-name] [model-version] <model-email>
Rules:
git diff and git status to understand all uncommitted changesgit add <specific files> — avoid git add -A unless all changes should be committedgit commit -m "$(cat <<'EOF'
🔧 Title of the change
Summary of the change, respecting the 100-char line limit.
Add more lines only if the change is complex enough to warrant it.
EOF
)"
With co-authorship:
git commit -m "$(cat <<'EOF'
✨ Title of the change
Summary of the change.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
EOF
)"
git status to confirm the commit succeededUse the model name and version from the current environment. The model ID claude-sonnet-4-6 becomes Claude Sonnet 4.6. Format:
Co-Authored-By: Claude [Model Name] [Version] <noreply@anthropic.com>
| Mistake | Fix |
|---|---|
| Title over 100 chars | Shorten — cut adjectives, use imperative verbs |
| Summary too long for a trivial change | 1 line is enough for small fixes |
| Adding co-authorship unprompted | Only add when user explicitly requests it |
Using git add -A blindly | Stage specific files to avoid committing secrets or unrelated work |
Skipping git status after commit | Always verify the commit landed correctly |
Use when writing or modifying end-to-end tests in the Alkaa project — triggers on tasks like "add an E2E test", "write a flow test", "test this feature end-to-end", "add a test to shared module", or "cover this user journey with a test".
Use when writing or modifying UI/Compose instrumented tests in the Alkaa project — triggers on tasks like "add a UI test", "test this composable", "add instrumented test", "test this screen behavior".
Use when adding, editing, or reviewing user-facing strings in the Alkaa project — UI labels, button text, content descriptions, empty states, error messages, plurals, or any text visible to the user.
Use when adding a new screen or modifying navigation in the Alkaa project — triggers on tasks like "add a new screen", "navigate to X", "add destination", "wire up navigation", or "create a navigation event". Also triggers when connecting UI actions to routes in NavGraph.
Use when creating a new Composable or modifying an existing one in the Alkaa project — screen structure, state handling, adaptive layouts, Kuvio usage, or previews.
Use when implementing a new Kuvio component for the Alkaa Design System after design spec and structure decisions are finalized