jmb-review-pr

Installation
SKILL.md

jmb-review-pr <n>

Review the PR of ticket <n> along the two axes of jmb-code-review (Standards and Spec) and leave the report as a comment on the PR. It is the flow's only review, sequential and parallel alike, and the human launches it after the ready.

Orchestrate from any checkout, and the working tree stays as it is: everything is read from origin/<branch>. That is why the ticket's worktree is not needed, which may also be half done if a fixer lives in it.

What is specific to the project comes from docs/agents/flow.md: each § is one of its headings, and each italic is the label of one of its fields. If the project does not have it, stop and ask for jmb-setup to be run.

Steps

  1. The PR. GitHub shares the number space, so <n> works as a PR and as a ticket: gh pr view <n> succeeds → that PR; it fails → the open PR whose branch starts with <n>- (gh pr list --state open --json number,headRefName,isDraft). Without a PR, stop and say so. Done when you have the PR number, the branch and the ticket of the Closes #<t> in its body, if it has one.

  2. Guards. In draft: stop, "come back when it is ready". CI pending or red (gh pr checks): stop. Reviewing a branch that is still going to change is wasted quota; the human decides whether to wait for green or take it out of draft. Done when the PR is ready and green.

  3. The fixed point. git fetch origin, and from there:

    git merge-base origin/main origin/<branch>      # the fixed point
    git diff origin/main...origin/<branch>          # the diff (three dots: against the merge-base)
    git log origin/main..origin/<branch> --oneline  # the commits
    
Installs
2
First Seen
3 days ago