How do I install the Review skill?

Run npx skillmds@latest add sbnet/review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Review safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Review?

sbnet (@sbnet) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Review by sbnet — Agent Skill

Name: Review
Author: sbnet

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.

sbnet ec35b78 2.1 KB Updated Sep 17, 2026

File contents

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

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).
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

Summary comment. Look for an existing PR comment containing the  marker (gh pr view <number> --json comments). If found, edit it in place so repeated runs update one comment instead of piling up:
```
gh api -X PATCH repos/{owner}/{repo}/issues/comments/<comment-id> -f body="
…"
```
Otherwise create it: gh pr comment <number> --body " …".

Inline comments, one per finding tied to a specific line:

gh api repos/{owner}/{repo}/pulls/<number>/comments \
  -f body="…" -f commit_id="<headRefOid>" -f path="<file>" \
  -F line=<n> -f side=RIGHT

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.

---name: reviewdescription: 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: review## PurposeReview the current branch's PR the way a human reviewer would, and postthe findings on the PR itself: one summary comment plus inline comments onspecific lines. There is no CI-based review to wait for or trigger: thisis the only way to get one, run locally by the user whenever a pass isactually wanted, typically once CI is green and before merging.## Preconditions1. 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: ReviewRun the `pr-review` subagent on this PR. It reads the diff and thesurrounding code and returns a compact findings list; that reading iswhere the bulk of the token cost sits, so it happens in the subagent's owncontext, not this session's.## Step 2: Post1. **Summary comment.** Look for an existing PR comment containing the `` 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=" …" ``` Otherwise create it: `gh pr comment <number> --body " …"`.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.

Frequently asked questions