菜单
Manage the PR lifecycle — open, check CI, and merge pull requests. Use when the user wants to open a PR, check whether a PR's CI passed, see if a PR is ready, or merge a PR. Covers the open/check/merge flow with the guardrails that the work goes on a branch and CI is green before merging. Not for code review (that's a separate task).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | pr |
| description | Manage the PR lifecycle — open, check CI, and merge pull requests. Use when the user wants to open a PR, check whether a PR's CI passed, see if a PR is ready, or merge a PR. Covers the open/check/merge flow with the guardrails that the work goes on a branch and CI is green before merging. Not for code review (that's a separate task). |
Open, check, and merge PRs with gh. The recurring mistakes this prevents:
working on main, and merging before CI is confirmed green.
main. If there are uncommitted changes on
main, git checkout -b <branch> before committing. See [[branch-before-changes]].
Pick a branch name that matches the scope of the work, not one narrow file —
if it may grow, name it broader (add/skills, not add/release-skill).-u, then gh pr create with a title and a body that
summarizes what changed and why.gh pr view <number> — state (open/merged/closed), title, body, comments.
Read existing comments before adding your own so you don't repeat the thread.gh pr checks <number> — one-shot status. Add --watch to block until checks
finish.gh run view <run-id> --job <job-id> --log
and grep for the failure.Do all three verifications, in order, every time:
gh pr view <number> — confirm it is still OPEN. Don't assume; it may
already be merged or closed.gh pr checks <number> — every check passed. Never merge on red or pending.gh pr merge <number> --squash (default to squash unless told otherwise).If anything is red or pending, stop and report — do not merge.
main.