Menu
Stage the right changes and write a clear, conventional commit message.
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
Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the `gh` CLI or the GitHub MCP server.
Systematically diagnose and fix a bug instead of guessing.
Add clear docstrings/comments and update docs for changed or unfamiliar code.
Map and explain an unfamiliar codebase or module to the user.
Improve code structure in small, safe steps without changing behavior.
Add focused, meaningful tests for code — happy path plus the edge cases that matter.
| name | Commit (clean, conventional) |
| description | Stage the right changes and write a clear, conventional commit message. |
| triggers | ["commit","git commit","write commit message"] |
Use this when the user asks to commit work. Produce a focused commit with a message that explains why, not just what.
git status and git diff (and git diff --staged) to see exactly
what changed. Read the changes — do not commit blind.git add -A without checking what it picks up.type(scope): summary, <=72 chars):
feat / fix / refactor / docs / test / chore. Add a body explaining the
reason and any trade-offs when the change is non-trivial.