flow

Delivery · Portable skill

review/

Review work in a fresh context against intent, the spec, and root context, on top of /code-review, and repair confirmed defects; "review only" stays read-only.

npx skills add gaboesquivel/flow-skills -s review

Say it

Natural language is the interface. Any of these, or your own words, reach the skill.

  • “review it”
  • “deep review”
  • “check it against the spec”
  • “does this match the intent”

When to use it

A fresh-context review through flow-reviewer on top of /code-review, with requirement verdicts, scope, glossary, and DESIGN.md checks. Writes fixes for confirmed defects; "review only" writes nothing.

The skill

The authoritative, versioned instruction your agent follows, from skills/review/SKILL.md.

Outcome

"Review it" gets an independent read and ends in repaired work: confirmed defects fixed and verified, or left unresolved with the reason. The author is never the reviewer. A spec's proof is a verdict on each acceptance scenario step (satisfied, unmet, or unresolved), each with evidence.

Claude Code's /code-review hunts bugs and /security-review checks trust boundaries. The plugin's flow-reviewer agent runs them and adds Flow's checks. Without that agent or /code-review, run these steps yourself and label the review single-agent.

Effort

build's Size guard picks the tier from the change, never its author, for a standalone "review it" too; "deep review" runs Deep. Tiers map to /code-review levels: Quick → low, Standard → medium, Deep → high.

Inspect

Scope: the working tree by default, or a branch, pull request, or spec. Run flow-reviewer with head, tier, and spec or request. It adds:

  • scenario verdicts: no evidence means unresolved, and unmet is Important
  • scope against build's Scope guard
  • names against GLOSSARY.md, flagging a missing entry only when it creates a meaningful ambiguity or naming inconsistency
  • owner commitments: when the change touches what PRODUCT.md, DESIGN.md, ARCHITECTURE.md, or GLOSSARY.md states, compare it with that statement
  • DESIGN.md and UI basics when the diff changes UI, including material experiential defects (a missing loading, empty, or error state) seen in the rendered result; a whole-journey walk is experience's

Be able to explain the consequential choices the change made. Findings cite file:line: Important (blocks), Nit (at most three), or Pre-existing (never blocks).

Repair

Fix each Important finding and unmet step on the branch, covering its whole bug class, with a check that fails without the fix when the bug could return unnoticed. Answer every other finding: fixed, or resolved with reason. "Review only" or "don't fix" stays read-only. Inside build, the main thread repairs. A re-review covers only the new diff and never repeats a finding. After three rounds with an Important finding open, stop patching and rethink the approach; fix a recurring finding at its source (a lint rule, skill, or AGENTS.md).

Report

A count ("2 Important, 1 Nit"), then scenario verdicts, findings by severity, repairs, and open items. On GitHub, post it as a comment, never an approval.

Jump to, or try a question