Skip to content
Development
Skill

/review-guide

Computes a PR's Tier floor and unplanned-changes list with a bundled read-only script, then writes the PR's Tier line and Review guide (decisions not in the plan, files to read closely vs skim, what to check by hand), and once the PR is open links each file to its diff. Use at

From plugin
ai-workflow
59 skills4 agents2 MCP

Claude Code

$ npx -y skills add cunhaax/ai-workflow --skill review-guide --agent claude-code

SKILL.md

review-guide.SKILL.md
name: review-guide
description: >
  Computes a PR's Tier floor and unplanned-changes list with a bundled
  read-only script, then writes the PR's Tier line and Review guide (decisions
  not in the plan, files to read closely vs skim, what to check by hand), and
  once the PR is open links each file to its diff. Use at /feature step 9
  before and after opening the PR, or when the user asks for a review guide for
  the current branch.
license: MIT
compatibility: Requires git and a POSIX sh with awk; file links use sha256sum or shasum when present.
metadata:
  author: André Cunha

/review-guide

Gives a reviewer a short guide to where to look in a PR, split by trust: a script computes the parts that must be trustworthy, and you write the parts that need judgment. `/feature` step 9 calls this skill; it can also be run on its own. It returns text for the caller to place. It never opens, edits or comments on a PR.

Input

  • The default branch (`AGENTS.md` → *Commands*)
  • The plan source, one of: the plan file's absolute path (the one `/feature`

last wrote, at step 1d or on a rewrite after re-approval, or `--from-plan` read); `--plan-reapproved` (a `--from-plan` run re-approved at step 2, so its saved plan is stale); or nothing (no plan file was saved). Run standalone with none given → ask for the path or "none"

  • The approved plan text's **Tier** line and the session's context (deviations,

decisions made while implementing)

  • The PR URL, once the PR is open (the one `gh pr create` printed; on a re-run

in a resumed session, `gh pr view --json url -q .url`; never build it by hand). Without it, step 4 does not run

Steps

1. Run the script

`sh ${CLAUDE_SKILL_DIR}/review-guide.sh <default-branch> [<plan-file> | --plan-reapproved]`

  • Any non-zero exit, any stderr, empty stdout, an unexpanded

`${CLAUDE_SKILL_DIR}` or a missing script → STOP per `AGENTS.md` Rule 2; never guess a path or work around it

  • A `not computed` reason other than `no plan file` or the re-approved one →

tell the user before going on

  • Syntax, exit codes and limits are in the script's header comment

2. Tier line

`**Tier:** <n> — <reason>`

  • n = the higher of the plan's tier and the script's floor (2 when it lists

sensitive paths). A `set by user` plan line counts as the higher of its two values, and shows both (`1 (set by user; derived 2) → 2`)

  • A judged prose area (step 3, not `unsure`) also raises n to 2, named in the

reason as `<area> (judged, not computed)`; it never lowers n

  • The plan's tier is the approved plan text's `**Tier:**` line (inside

`/feature`, the one in context). Standalone, read it from the given plan file; with no plan, n is the floor, marked "no plan tier"

  • The reason names each sensitive area touched, as a fact
  • Floor or a judged area above the plan's tier → tell the user before the PR

opens: `/feature` step 4's `opus` override and second reviewer may not have run, and the user decides whether to run them now (inside `/feature`: `build.md` step 4 on HEAD with both, counting as the second reviewer's first run if it has not run, else its one extra run (already used → the user decides whether to exceed it), then steps 5–6, steps 7–8 again if a fix touches a UI or API surface, then this skill again)

3. Review guide

For the reviewer; commit SHAs are allowed here.

  • The script's stdout, verbatim, first
  • **Prose Sensitive Areas (judged, not computed)** under it, when the script

prints `Not path-checked: <k>` or the branch's `AGENTS.md` diff removes a prose-only bullet (no leading backticked path, not a `[TODO` placeholder; read `git show HEAD:AGENTS.md` plus the removed ones, marked ` (removed on this branch)`). One line per area, named by its text before ` — `: each changed file whose diff changes behaviour it describes, `` `<path>` — <reason> `` (not mere nearness; if unsure, reason `unsure`), else `none judged`. Your count differs from `<k>` → say so

  • **Decisions not in the plan**: one line each; every unplanned path

accounted for, or "None"

  • **Read closely** / **Skim**: paths, one line why each. Copy each path from

`git -c core.quotepath=off -c diff.relative=false diff --no-renames --name-only <base ref from the script's header>...HEAD`, never type it from memory

  • **Check by hand**: what to try in the running app, or "nothing: no UI or API

surface"

4. Links

Only with a PR URL and a non-empty **Read closely** or **Skim**; with both empty, skip it (the caller's incomplete-guide rule does not apply).

`sh ${CLAUDE_SKILL_DIR}/review-guide.sh --links <pr-url> <path>...`

  • One call: pass every **Read closely** path, then every **Skim** path, in

single quotes when it has spaces or shell-special characters

  • Its lines replace those entries (split back into the two lists by argument

order); append ` — <why>` to each. A `Links: not computed (…)` line goes verbatim once under the lists, and tell the user

  • Exit 1, any stderr or empty stdout → STOP per `AGENTS.md` Rule 2. Report the

PR URL, the error and the guide with plain paths, ready to post by hand; the plan file stays unconsumed

  • Never write a link by hand

Output

The Tier line and the Review guide. The caller puts the Tier line in the PR description and the guide at the top of the first comment. Before the PR opens the entries are plain paths; step 4 links them once it is open, and the description never carries links. Run again, and replace both, after any commit made once the PR is open (including step 4).

Rules

  • Never alter, trim or contradict the script's output; an omission in your own

parts must stay visible next to it. Its `→ none` covers computed paths only, so a judged raise beside it is not a contradiction

  • Step 4's lines are entries to extend with ` — <why>`; never drop or reorder

one or edit its path

  • Never put the plan file's absolute path in the output: the script prints the

basename only

Read more
@cunhaax
Ships withai-workflow

Turns Claude Code into a small development team instead of one agent guessing alone — with a git-level gate that keeps the humans in charge of what actually ships.

59 skills4 agents2 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
5
Star history of cunhaax/ai-workflow on GitHub, a chart by star-history.com

Other skills on ai-workflow.

adversarial-qa

adversarial-qa

Exploratory QA of a running feature through its UI (Playwright) and/or API (curl) to find issues the plan and committed tests…

@cunhaax@cunhaaxInstall Skill
code-critic

code-critic

Reviews code changes against project standards and the approved plan; returns PASS/FAIL/NEEDS_DECISION per checklist item plus…

@cunhaax@cunhaaxInstall Skill
feature

feature

Runs the full AI-assisted workflow for a non-trivial feature or change: plan, plan critique, user approval, implementation with…

@cunhaax@cunhaaxInstall Skill
init-workflow

init-workflow

Sets up and checks the AI workflow in a project that has this plugin installed: scaffolds missing AGENTS.md, CLAUDE.md, hooks,…

@cunhaax@cunhaaxInstall Skill
plan-critic

plan-critic

Critiques a draft implementation plan with pre-mortem, inversion, load-bearing-assumption and consistency checks; returns…

@cunhaax@cunhaaxInstall Skill
plan-draft

plan-draft

Drafts a structured implementation plan (approval summary with acceptance criteria, contract, files, edge cases, test strategy)…

@cunhaax@cunhaaxInstall Skill

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills12d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc13d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react2d252k
@facebook@facebookInstall Skill

Questions about review-guide.

Which coding agents can use review-guide?
review-guide installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.