菜单
Runs the full PR checklist by chaining the pr-* skills in a logical order. Use when a branch should be taken end-to-end to a healthy, review-ready PR.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | pr |
| description | Runs the full PR checklist by chaining the pr-* skills in a logical order. Use when a branch should be taken end-to-end to a healthy, review-ready PR. |
| user-invocable | true |
| disable-model-invocation | false |
Orchestrate the pr-* skills as one checklist for the current branch; do no PR work directly outside those skills.
Each step follows its own skill's contract and safety rules.
Follow CLAUDE.md / AGENTS.md on conflict.
Run in order, skipping steps the user excluded.
changes:
branch, and commit, then proceed to step 2b.commitpr-info: resolve and verify the PR.pr-comments: diagnose existing failed CI jobs and apply fixes locally; instruct it to defer push.pr-ci: apply fixes for unresolved threads locally; instruct it to defer push and thread replies.pr-create: create a new PR.pr-rebase: rebase onto the latest base and force-push with lease. This single push carries all fixes and triggers one fresh CI run and review-agent pass.pr-description: sync the PR body with the final changeset.After each step, report its outcome before continuing. Stop and ask when any step hits its own stop gate, fails, or leaves the branch in an unexpected state.
Report a per-step checklist (run/skipped/blocked with one-line outcome), final PR URL and state, and any unresolved blockers.
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Splits a large branch or PR into smaller, independently reviewable units by grouping changes and proposing parallel PRs or a stacked series. Use when a changeset is too big to review well and should be broken up.
Captures the portable, non-secret pi config from a live ~/.pi/agent into this repo's pi/ directory and commits it, without reading or copying secrets. Use when live pi config or extensions have drifted from the repo and need to be synced back.
Refreshes PR titles and descriptions to match the current branch changeset. Use when the PR title or body has drifted from the code.
Reviews the current session for problems and their eventual fixes, then proposes durable improvements to repo skills, scripts, or docs that prevent recurrence. Use when a session hit avoidable friction worth turning into a lasting fix.
Runs discovery and uncertainty resolution for a change, then writes a terse plan document covering purpose, behaviour, validation, architecture, and phased vertical slices. Use before building when a change needs a clear, agreed design.