菜单
Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Approve a pull request using gh pr review --approve
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.
| name | post-review-comments |
| description | Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style |
| targets | ["*"] |
target_pr = the user's request
If target_pr is not provided, use the PR of the current branch.
Read the PR diff and description to understand:
Identify specific lines in the diff that deserve feedback — bugs, potential issues, style concerns, suggestions for improvement, or questions about intent.
For each comment, note:
Write a brief overall assessment of the PR. This is a summary-level comment, not a repeat of line-level feedback.
Use a single gh api call to submit both line-level comments and the overall comment together as one review:
gh api repos/{owner}/{repo}/pulls/{pr_number}/reviews \
--method POST \
-f event="COMMENT" \
-f body="<overall comment>" \
-f 'comments[]={...}' ...
Each line comment requires: path, line (line number in the diff's new file), and body.
If you have no line-level comments, fall back to:
gh pr review <pr_number> --comment --body "<overall comment>"
Write in English only.
Style guidelines — write like a human teammate, not a bot:
##), horizontal rules (---), and excessive bullet lists.Output the PR number, a count of line-level comments posted, and a brief summary of the overall comment.