Menu
Prepare high-quality git commit messages or comprehensive Pull Request (PR) descriptions based on recent changes.
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
Ensure this skill is active before every journal write — new entry, edit, restructure, or activity log append. Provides the graph protocol (bidirectional links, indexes), the directory layout, and the activity log format that keep the journal consistent.
Activate when the turn's deliverable is source, test, code analysis, or config files — editing or creating code. Provides the Research → Strategy → Execution workflow, the complexity budget, and specialised deep-dive companions (testing, debug, refactor, review).
Activate when the turn's deliverable is a design — system architecture, API contract, data model, component decomposition, or trade-off analysis. Provides the Constraints → Explore → Decide → Specify → Plan workflow for sound, well-reasoned designs.
Activate when the turn's deliverable is findings, comparisons, recommendations, or an investigation-backed plan — answering questions, analyzing unfamiliar code, exploring new domains. Provides the systematic Scope → Discover → Synthesize → Plan workflow.
Activate when the turn's deliverable is substantial prose — docs, copy, proposals, feedback, commit/PR text, or UI strings. Provides copywriting frameworks, tone guidance, and editing workflow for clear, persuasive, polished output.
Force explicit research mode — Scope → Discover → Synthesize → Plan — with the approval gate before any implementation.
| name | git-summary |
| description | Prepare high-quality git commit messages or comprehensive Pull Request (PR) descriptions based on recent changes. |
| user-invocable | true |
| disable-model-invocation | true |
When this skill is activated, you assist the user in drafting professional version control summaries.
git status and git diff (or git log) to thoroughly understand the changes since the last commit or base branch.git commit -m "$(cat <<'EOF'
[Subject line]
[Body explaining the why]
EOF
)"
Note: Default to providing the draft and the exact command for the user to review and execute. Run the commit or create the PR yourself only when the user explicitly asks you to — and then follow the Git Rules: show git status + git diff HEAD and obtain approval first.