review
Review an implemented draft pull request as an agent that did not write it, fix small findings or hand it back, then mark it ready and babysit it to merge. Use when a draft PR waits on review, or when asked to review and land one.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- review
- description
- Review an implemented draft pull request as an agent that did not write it, fix small findings or hand it back, then mark it ready and babysit it to merge. Use when a draft PR waits on review, or when asked to review and land one.
02 资源文件 2
- 参考文档CREDITS.md99 B
- 脚本round.mjs9.5 KB
03 SKILL.md 正文
A prompt or brief naming this skill is its invocation.
Take an implemented draft pull request to merge as its independent reviewer.
Run in a session that wrote none of the change; if you wrote any of it, stop
and say so, because the review needs a fresh agent. The
github-repository-configuration rules' Review of an implemented pull request
section holds what a review must do, and where installed, the
factory-workflow rules hold how an owner gate stops it; this skill supplies
the method. Each step that posts names the section of
.repo-standards/rules/comments.md to read before posting.
The review works in rounds, one reviewed head each. A round holds, hands back, fails or goes to a grill, as those rules say.
node <this skill's directory>/round.mjs <number>, run from the repository
root, prints the PR's head, its round, whether that head is already
reviewed, whether the review held, whether it is a draft, the issues it
closes and every owner gates label on the PR or those issues. It counts
only the standing reviews of the account you run as, as the rules say: the
review held when that account's latest one is a holding review of the head.
Add --issue <n> for an issue the PR links without closing. It requires
Node.js 24 or 26 and uses the GitHub CLI's credential. Exit 1 is an
invocation or platform error, including more closing issues or labels than one
read holds: follow CONTRIBUTING.md's Credentials section for a permission
refusal; otherwise fix the cause and run it again.
- Read the round. Run
round.mjs. When it reportsheld yes, delivery already started, as after a run stopped before step 5 finished, a later babysit round or a cleared gate: go to step 5. When it reportsreviewed yesandheld no, your round on this head left a finding open: stop and report that the head waits for the implementation or grill its review asked for. Otherwise read the authoritative implementation contract underCONTRIBUTING.md's Implementation contracts section, the whole issue and its discussion, and every earlier round's review. A PR without an issue takes its decision-bearing body as its contract. Done when you hold the head, the round number, the contract and the issue. - Review. Check out the head in a checkout you own and run
code-reviewwith the merge-base of the PR's base branch as the fixed point and the contract as the spec. Applycodebase-design's Ownership check throughcode-review's Standards axis, judging against the recorded contract. Give its Spec axis this task context: also read the contract against the issue, and report where the contract contradicts, drops or invents what the issue and its recorded decisions ask, or leaves it ambiguous. A PR without an issue has no such check. Verify every finding against the source and drop those that do not hold. A defect outside the change's responsibility goes underCONTRIBUTING.md's Findings section, not into this review. Sort each remaining finding as contract, larger or small, by the rules' section. Done when every finding from both axes is dropped with its reason or sorted. - Fix small findings when no contract or larger finding stands; otherwise
fix nothing and carry every finding into the review. Commit the fixes to the
PR branch, run the required checks the development guide names, and push.
Run
round.mjsagain: its head is the head this round's review covers. Done when the diff from the reviewed head to that head holds only the fixes and the checks pass. - Post the round's review, after reading
.repo-standards/rules/comments.md#reviews: the actual Standards and Spec outcomes, the fixes underFixed, and each open finding underFindingswith its file and line, all in its body, listing only the findings the rules count as open. Post it withround.mjs <number> --post <file>; exit2means the file is not a complete review of the current head, so correct it and post again; exit3means this head already has your review, so post none. Then:- The round holds: go to step 5.
- A larger finding in round 1 hands back: leave the PR a draft and
end the run, reporting the hand-back with the review's link, so
implementcan take it on the same PR. - A larger finding in a later round fails: leave the PR a draft and end the run, reporting that the rounds did not converge and why.
- A contract finding: post the question a grill must settle as
.repo-standards/rules/comments.md#owner-questionssays, move the issue tostate:grill, leave the PR a draft and stop underCONTRIBUTING.md's owner-question handoff.
- Deliver. Mark the PR ready with
round.mjs <number> --ready; exit2means the review has not held, so return to step 1. Then runbabysiton the PR, posting each internal review round it calls for withround.mjs --post, in the same shape as step 4. Before each of babysit's merge attempts, runround.mjsagain. When it reports a gate, stop at ready-to-merge as thefactory-workflowrules say: leave the PR open, move its issue, if it has one, tostate:owner, and end the run, reporting the gate.
Reads
Paths are relative to the repository root.
CONTRIBUTING.md: the implementation contract, Findings, Credentials and owner-question handoff the steps name, and the development guide's required checks. When it is missing, take the issue body as the contract, run the checks the repository documents, and hand off to the owner in one PR comment for any rule the steps leave to the guide..repo-standards/rules/comments.md: the installed comment rules, whose sections the steps name before each post. When it is missing, post each review in the shaperound.mjsaccepts and each question as one comment.- The installed
github-repository-configurationandfactory-workflowrules, and thosebabysitnames, which therepository-standardsskill looks up. When the review section is missing, hold a round only with no open finding, hand back any other finding once and fail on a second round with one; without the factory rules, a gate stops delivery as step 5 says. - The
code-reviewskill, which runs both axes. When it is missing, review the diff since the merge-base against the repository's documented standards and against the contract yourself, keeping the two axes apart. - The
babysitskill, which delivers the PR:round.mjsimports its GitHub CLI connection and its review shape. When it is missing,round.mjscannot start: stop and report that this skill needs it. - The
implementskill, which takes a hand-back on the same PR. When it is missing, report the hand-back with the review's link and stop. - The
codebase-designskill: the check used through Standards above. When missing, report the gap through the contribution guide's Findings route, or in the handoff without the guide; retain the recorded contract as the baseline.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
triage
Move issues and external PRs through a state machine of triage roles, sort each request by where its uncertainty lies, and bring its agent brief to acceptance through research and independent review, or through a grilling session with the owner. Also runs unattended as the factory's triage run, which writes nothing and ends with a run result.
to-tickets
Break a specification into independently mergeable tickets, publish them in their responsible repositories with native parent and blocking links, and return the split for independent review.
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.