메뉴
Push the current branch and create a pull request with a title and description derived from the commit history. Use when the user asks to open a PR — the Ship step of the Orchestrator loop, always user-triggered.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Run a PR's full review-fix cycle — wait for review and CI, fix failures, evaluate and reply to comments, then commit and push. Use whenever a PR was just opened or updated — the post-Ship phase of the Orchestrator loop.
Delegate a task's implementation wholesale to OpenAI Codex (`codex-run work`) — the whole requirements document in one long autonomous run — keeping policy, orchestration, and acceptance in the main loop. Use at the Implement step of the Orchestrator loop, for any multi-part build.
Cross-model second opinion from OpenAI Codex — `codex-run advise --context` reviews the current session, or pipe a brief. Triggers on "ask codex", "codex review", "second opinion", or the "Cross-model review" rules.
Define requirements before implementation — clarify constraints and design policy, then write a requirements spec and task breakdown for the Implementer to a gitignored plan file. Use at the Plan step of the Orchestrator loop, or whenever a request's scope needs pinning down before building. Never implements; the plan file is its only write.
Root-cause investigation — enumerate competing hypotheses, verify each with evidence, suggest a fix but never apply it. Use when an error, failing test, or anomaly needs diagnosing before any fix is written; implementation hands off to the Implementer.
Create, improve, and evaluate skills. Use when the user wants to create a skill from scratch, edit or optimize an existing one, run evals or benchmarks on it, or optimize its description for better triggering accuracy.
| name | pr |
| description | Push the current branch and create a pull request with a title and description derived from the commit history. Use when the user asks to open a PR — the Ship step of the Orchestrator loop, always user-triggered. |
| argument-hint | [base-branch] |
| allowed-tools | ["Bash","Read","Grep","Agent"] |
/pr [base-branch]
Argument interpretation:
main as base branchCURRENT=$(git branch --show-current)
BASE=${1:-main}
maingit log --oneline $BASE..HEADGather context in parallel:
git log --oneline $BASE..HEAD — all commits in this branchgit diff --stat $BASE..HEAD — files changed summarygit diff $BASE..HEAD — full diff for understanding the changesIdentify:
Title: Under 70 chars, Conventional Commits style (feat(scope): description)
Body: Use this template:
## Motivation
Why this PR is needed — the problem, user pain, or business context driving the change.
## Summary
- Bullet points explaining WHAT changed
## Changes
- Key changes grouped by logical unit
## Test plan
- [ ] How to verify the changes
@codex review
Then end the body with your standard attribution footer. The @codex review line triggers Codex's automated review as a backstop in case repo auto-review is off; drop it for repos where Codex isn't configured.
git push -u origin $CURRENT
gh pr create --base $BASE --title "..." --body "$(cat <<'EOF'
...
EOF
)"
Output the PR URL.
main directly--base flag to specify target branchgh pr create fails due to existing PR, show the existing PR URL instead