Menu
Review local docs and create a git commit or pull request. Use when committing changes with documentation review, or opening a PR.
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
Grilling and design session that challenges your plan against the existing codebase, domain model, and documented decisions; sharpens terminology; updates documentation (CONTEXT.md, design docs) inline as decisions crystallize; and produces committable implementation plans. Use when user wants to stress-test, design, or plan a feature against their project's language and documented decisions.
Grilling and design session that challenges your plan against the existing codebase, domain model, and documented decisions; sharpens terminology; updates documentation (CONTEXT.md, design docs) inline as decisions crystallize; and produces committable implementation plans. Use when user wants to stress-test, design, or plan a feature against their project's language and documented decisions.
Capture polished screenshots of terminal applications and TUIs. Use before terminal-control when the user wants a terminal screenshot or live TUI state documented.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets, and resolve them one at a time until the way to the destination is clear.
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help commiting code, writing commit messages, or reviewing staged changes.
Use at the end of a unit of work, before commit or PR, to verify related documentation matches the new state
| name | gc |
| description | Review local docs and create a git commit or pull request. Use when committing changes with documentation review, or opening a PR. |
A composite workflow that ensures documentation is up-to-date before committing changes.
CRITICAL: This skill delegates to sub-skills. You MUST use the Skill tool to invoke each one — do NOT attempt to perform their work inline from memory or summary knowledge. The sub-skills contain detailed procedures that must be followed.
Execute these steps in order:
Invoke the update-docs skill and follow its instructions.
After the documentation review skill completes, stage any documentation files that were modified:
git add <updated-docs-only>
Only stage documentation files that were actually modified. Do not git add . — there may be unstaged files not ready for commit.
Invoke the commit-msg skill. Skip any steps (like reading the diff) already completed during step 1.
If the user asks to open a PR instead of (or after) committing, follow the procedure in references/pr.md.