# Review

> Review the current branch's PR and post the findings as comments on it. Use when the user asks to run/launch/trigger a review, or the feature/gh-pr flow reaches the point where CI is green and a review is worth requesting before merge.

- Skill: `sbnet/review` (Agent Skill)
- Install (CLI): `npx skillmds@latest add sbnet/review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sbnet/review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: sbnet (https://skillmd.com/u/sbnet)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sbnet/review

---


# Skill: review

## Purpose

Review the current branch's PR the way a human reviewer would, and post
the findings on the PR itself: one summary comment plus inline comments on
specific lines. There is no CI-based review to wait for or trigger: this
is the only way to get one, run locally by the user whenever a pass is
actually wanted, typically once CI is green and before merging.

## Preconditions

1. Find the PR for the current branch: `gh pr view --json number,url,headRefOid`.
   If there is none, tell the user to open one first (`/flux:gh-pr`).
2. Everything meant to be reviewed must already be pushed: review the
   PR's head commit (`headRefOid`), not uncommitted local changes.

## Step 1: Review

Run the `pr-review` subagent on this PR. It reads the diff and the
surrounding code and returns a compact findings list; that reading is
where the bulk of the token cost sits, so it happens in the subagent's own
context, not this session's.

## Step 2: Post

1. **Summary comment.** Look for an existing PR comment containing the
   `<!-- flux-review -->` marker (`gh pr view <number> --json comments`).
   If found, edit it in place so repeated runs update one comment instead
   of piling up:
   ```shell
   gh api -X PATCH repos/{owner}/{repo}/issues/comments/<comment-id> -f body="<!-- flux-review -->
   …"
   ```
   Otherwise create it: `gh pr comment <number> --body "<!-- flux-review -->
   …"`.
2. **Inline comments**, one per finding tied to a specific line:
   ```shell
   gh api repos/{owner}/{repo}/pulls/<number>/comments \
     -f body="…" -f commit_id="<headRefOid>" -f path="<file>" \
     -F line=<n> -f side=RIGHT
   ```
3. Never approve the PR, never submit the review as a chat message
   instead of a comment: the comments on the PR are the deliverable.
   Merging stays with the human.

Report the comment URLs to the user, then continue with
`/flux:gh-address-comments` for the triage.