菜单
Push a reviewed ticket branch and open a pull request with a structured title and body, after review-changes has passed. Use when a ticket is reviewed and ready to ship, or the user says "open a PR" / "create the pull request". Stops at opening the PR — never merges.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run a bounded change → verify → fix cycle until an objective check passes (tests green, lint clean, build/type-check ok) or a hard iteration cap is hit. Use for any task that needs repeated attempts against a verifiable signal instead of a single one-shot edit.
Review code for behavior-preserving simplification — collapse duplication, remove dead code and over-engineering, cut verbose patterns down to idiomatic ones. Use when code is longer or more complex than it needs to be, or the user asks to simplify, shorten, refactor, or clean up.
Implement a planned ticket on its own branch using test-first development, updating docs as part of the change, looping change→verify→fix until the suite is green. Use when a ticket has a plan and is ready to build, or the user says "implement X" / "build the ticket" / "make it pass".
Use to store durable context (decisions, facts, preferences, todos, summaries) and to recall or reply from it across sessions. Load when something worth remembering appears, or when the user asks what you were doing, what was decided, or to continue prior work.
Choose the right model and effort per task phase and apply it when dispatching subagents — strong model + high effort for planning and review, a cheaper model + lower effort for mechanical execution. Use when a task splits into plan / execute / review phases or you're spawning subagents.
Turn a feature request into a concrete plan — scope, approach, affected files, a test plan mapped to acceptance criteria, and out-of-scope — before any code is written. Use when the user describes new work, asks to design or spec something, or says "plan this" / "how would you build X".
| name | open-pr |
| description | Push a reviewed ticket branch and open a pull request with a structured title and body, after review-changes has passed. Use when a ticket is reviewed and ready to ship, or the user says "open a PR" / "create the pull request". Stops at opening the PR — never merges. |
| model | sonnet |
| effort | medium |
| allowed-tools | ["Read","Bash"] |
| argument-hint | <ticket id> |
| triggers | ["open a pr","create the pull request","push and open pr","ship it"] |
| tags | ["pr","github","git","pipeline"] |
Turn a reviewed branch into a pull request. This is pipeline step 5 (plan → track → implement → review → pr) and the last step — it opens the PR and stops.
Never merge; a human reviews and lands it.
node "${CLAUDE_PLUGIN_ROOT}/hooks/pipeline.mjs" show <ticket-id>
If the review step isn't done, STOP and run review-changes first. Do not
open a PR for unreviewed code.
BR=$(node "${CLAUDE_PLUGIN_ROOT}/hooks/pipeline.mjs" branch <ticket-id>)
git checkout "$BR"
git push -u origin "$BR"
DEFAULT=$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|origin/||' || echo main)
Compose the PR with a HEREDOC body (never a fragile one-line --body):
gh pr create --base "$DEFAULT" --head "$BR" \
--title "[<ticket-id>] <ticket title>" \
--body "$(cat <<'EOF'
## Summary
<what changed and why, 1-3 bullets>
## Ticket
<ticket-id> — <title>
## Changes
<the notable files/areas touched>
## Test plan
<how it was verified: the suite that passed, key cases; review findings resolved>
EOF
)"
gh pr view "$BR" --json number,url
node "${CLAUDE_PLUGIN_ROOT}/hooks/pipeline.mjs" step <ticket-id> pr done --note "<pr url>"
node "${CLAUDE_PLUGIN_ROOT}/hooks/memory.mjs" keep "<ticket-id> PR opened: <url>" --kind summary --tags pr
review is done.gh is missing or unauthenticated, tell the user the fix (gh auth login)
and stop — don't fabricate a PR.Report the PR number and URL, and that it's ready for human review + merge. Under ship, this is the terminal step — return the PR URL.