菜单
Approve a pull request using gh pr review --approve
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | approve |
| description | Approve a pull request using gh pr review --approve |
| targets | ["*"] |
Approve a pull request using gh pr review --approve.
the user's request
Parse the user's request to identify the PR to approve:
123, #123, https://github.com/owner/repo/pull/123gh pr view --json number,title,state
If the PR cannot be determined (e.g., no PR exists for the current branch, or the argument is ambiguous), ask the user to specify which PR to approve.
Before approving, confirm the PR details:
gh pr view <pr_number> --json number,title,state,author,baseRefName,headRefName,isDraft
Check:
OPENisDraft is false)If the PR is not open or is a draft, inform the user and stop.
Execute the approve command:
gh pr review <pr_number> --approve
Important: Only approve ONE PR at a time. If multiple PRs are somehow specified, ask the user which single PR to approve.
If you want to add a comment along with the approval, use the --body option:
gh pr review <pr_number> --approve --body "<approval_comment>"
After approving:
Draft a new release of the project.
Form an Agent Team of Implementer and Reviewer subagents to tackle the given task, looping implementation and review until the Reviewer reports zero high-or-above findings and no more than three mid findings.
Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed), get every check green, and merge. Use when the user wants to shepherd a Dependabot bump PR to merge.
Resolve every open issue one at a time: fact-check each with web research, close the ones that need no action, and run the `goal-pr` skill to fix, review, and merge the ones that do — repeating until no actionable issues remain.
Resolve every open maintainer-scrap issue one at a time: fact-check each with web research, close the ones that need no action, and run the `goal-pr` skill to fix, review, and merge the ones that do — repeating until no actionable scrap issues remain.
Batch-triage open pull requests: list PRs with prs-awaiting-maintainer, review each with review-pr, then post-review-comments when there are merge-blocker findings, or create-scrap-issue for non-blocking findings and merge-pr when there are none. Use when the user wants to review and resolve a batch of PRs in one pass.