菜单
Use in /implement after committing, to push the feature branch and open a draft PR, returning the PR ref. Thin and GitHub-specific (gh) behind a host-neutral contract. Transitional — removed under the post-v1 flow simplification. Project-overridable for provisioning-heavy open steps.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use during /research (or any recipe) to send 1-3 research queries in parallel — vault or web targets — and aggregate compressed findings. Routes each query to vault-researcher or web-researcher based on target. Hosts the cross-verify consent gate so any inline-research caller (/research, /design, /decompose) inherits source-bias mitigation without duplicating logic.
Use at the start of /implement's repo path to land in a clean working state — fetch, fast-forward main, prune merged branches/worktrees/plan-files, then create the feature branch + worktree off fresh main. Repo-only; project-overridable for deep provisioning.
Use in /implement at the draft→ready boundary, before publish-pr's squash, to delete this branch's transient plan/spec artifacts so they don't ship in the PR. Deletes .claude/plans/<branch>.md (flattened name). Distinct from repo-setup's prune of previously-merged branches' artifacts.
Use in /implement at the draft→ready boundary to squash the branch's review-iteration commits into one (non-interactive soft-reset + recommit + force-with-lease) and mark the draft PR ready. Takes the commit message as input (sourced from the plan-file before cleanup). GitHub-specific (gh) behind a host-neutral contract.
Use in /implement after committing, inside the draft PR, to review the committed diff. Dispatches a dependency-free review subagent fed the diff + review criteria and returns structured findings (severity / location / problem / fix). The recipe drives the address→re-review loop with a human exit gate; the pr-review-toolkit ceiling is an opt-in override of this skill.
Use BEFORE writing implementation code in /implement, after repo-setup and once a ticket exists. Produces an approval-blocked plan at .claude/plans/<branch>.md (story ref, change summary, affected files, approach, test cases, open questions) and blocks coding until it exists and the user has approved it. Skip only for trivial changes, with an auditable one-line reason.
| name | open-draft-pr |
| description | Use in /implement after committing, to push the feature branch and open a draft PR, returning the PR ref. Thin and GitHub-specific (gh) behind a host-neutral contract. Transitional — removed under the post-v1 flow simplification. Project-overridable for provisioning-heavy open steps. |
Opens the draft PR that /implement's review step runs inside. Thin: push the branch, create a draft PR, return its ref. The PR is a draft (not ready) so review happens before it's "real" — and so pr-review-toolkit's PR-framed agents (when used via the agent-review ceiling) have a PR object to attach to.
All GitHub/gh coupling lives here and in publish-pr; the recipe and the other primitives stay host-agnostic.
repo-setup), already committed.plan-file / ticket.git push -u origin <branch>.gh pr list --head <branch> returns one), return its ref instead of creating a duplicate (gh pr create errors when one exists).gh pr create --draft --title "<title>" --body "<body>" — base = the repo's default branch, head = the current branch (gh infers both; pass --base/--head explicitly if those defaults don't apply). Add per-repo flags (labels, reviewers) per the project's agent-instruction file.gh output.agent-review and publish-pr can target it.create-pr.sh: templated body, labels, linked issues) overrides this, keeping the contract (branch → PR ref).publish-pr absorbs PR creation. Keep it thin so its removal is cheap.