Menu
Use when the user is working on their own PR — drafting/creating it, handling reviewer comments, verifying fixes, or requesting re-review.
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
Use when the user explicitly runs /setup-precommit to install or refresh a quiet, staged-only git pre-commit hook (secretlint → oxlint → oxfmt) wired through package.json "prepare". User-invoked command only, never auto-triggered.
Use when the user asks to create, make, or start a new branch (e.g. `/branch`), or wants a conventional-commit-style branch name generated from the current work.
Use when auditing or improving an agent skill package before it ships or is handed off.
Use when reviewing someone else's PR at any stage of the review lifecycle — digest a PR, write a review, or verify follow-up changes.
Use when fixing a bug, refactoring existing code without changing its behavior, or adding a feature that extends existing behavior — any code change that needs a verifiable foundation before the change is made.
Use when the user wants to A/B test prompts or workflows, validate behavioral equivalence, or stress-test non-deterministic outputs at scale via repeated multi-agent runs.
| name | pr-author |
| description | Use when the user is working on their own PR — drafting/creating it, handling reviewer comments, verifying fixes, or requesting re-review. |
Determine the sub-command from args or conversation context:
| Trigger | Sub-command | Action |
|---|---|---|
create, "PR 만들어", "PR 작성", no existing PR for branch | create | Read and follow create/index.md |
respond, "리뷰 반영", "피드백 처리", review feedback mentioned | respond | Read and follow respond/index.md |
| (no arg, ambiguous) | — | Auto-detect (see Auto-Detection) or ask the operator |
When no explicit sub-command is given:
gh pr view --json number,state 2>/dev/nullDetect the operator's conversation language. All generated content (summaries, comments, reports) MUST use that language. Preserve source-code artifacts (file paths, identifiers, diff hunks) in their original language.