Menu
Commit changes with smart messages. Supports full and partial commits. Use whenever committing changes or handling pre-commit hook failures.
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
Traces code history via git blame and log to explain why code exists in its current form. Use when asked about code history, reasoning behind changes, or "when/why did this change".
Use the gh CLI for GitHub interactions, plus setup and pushing. Use when interacting with GitHub, setting up GitHub tools, or pushing to remote.
Universal polyglot linting and per-project config management. Use when you need to lint files, understand tool selection logic, invoke linting from commands/agents, or manage mr-sparkle config.
Resolves git merge conflicts by analyzing intent from both sides. Use when merge conflicts are detected or when git operations fail with conflict errors.
Create a pull request with Problem/Solution format. Can optionally commit first. Use when opening PRs or when branch changes are ready for review.
User's README style preferences — ultra-terse, action-focused, <50 lines. Use when writing or reviewing any README file.
| name | commit |
| description | Commit changes with smart messages. Supports full and partial commits. Use whenever committing changes or handling pre-commit hook failures. |
| argument-hint | ["message","instructions","or description of what to commit"] |
Interpret arguments — $ARGUMENTS could be any of:
Use judgment based on context. Don't ask unless unclear — infer if possible.
Analyze repository state:
git status — see all changesgit diff and git diff --staged — see what's changedStage files:
git add .)Generate or use commit message following these requirements:
fix:, feat:, refactor:, etc.)Good: prevent race condition in session cleanup, rate limiting middleware
Bad: fix: correct bug, updates, add new feature ✨, fix bug.
Commit:
git commit -m "message"
Handle pre-commit hook failures:
Pre-commit hooks (formatters/linters) sometimes auto-modify files during commit, causing it to fail because git won't commit when the working directory changes mid-process.
git add . then git commit --amend --no-editgit log -1 --format='%an <%ae>' — never amend someone else's commitVerify: git status and git log -1 --oneline