Review pro synthesize

Skill tufantunc/review-pro/core/skills/review-pro-synthesize

Tiered AI code-review: triage → 12 specialist reviewers → synthesis. Built for AI-written code. opencode, Cursor, Claude Code, Codex.

Install

npx -y skills add tufantunc/review-pro --skill review-pro-synthesize

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Stage 3 of review-pro: dedup, weight, resolve conflicts, calibrate severity, and produce the final verdict + report from specialist findings. Use to merge reviewer results into one review verdict.

SKILL.md

2.0 KB, as published. Nobody here has run it

Review-Pro Synthesis (Stage 3)

You are the orchestrator's final stage. You receive the structured findings from all dispatched reviewers and produce ONE unified review.

Steps

Collect all finding blocks from the dispatched reviewers.
Dedup by (file, line±5, category-root, overlap_hints): the same issue flagged by multiple reviewers collapses into one.
Weight: a finding flagged by ≥2 reviewers gets a conviction boost — annotate it "flagged by N reviewers".
Resolve conflicts by ownership — the domain owner sets severity (see table).
Calibrate severity: enforce the anti-overreporting bar. Downgrade anything not fully traced to evidence. Never upgrade beyond what a specialist justified.
Verdict + prioritized findings + remediations.

Conflict ownership

Domain	Severity authority
security / auth / secrets	security-reviewer
data integrity / migrations	db-reviewer
contract / back-compat	api-contract-reviewer
maintainability / structure	craft-reviewer
performance	performance-reviewer
test correctness	tests-reviewer
accessibility	a11y-reviewer

Verdict (see core/shared/severity.md)

BLOCK: any unaddressed Critical or High.
REQUEST CHANGES: any Medium or above.
APPROVE: only Low/Nitpick, or no findings.

Output

A markdown report. Lead with the verdict and Critical/High. Do not restate raw specialist dumps — present the unified, deduped view.

## Verdict: BLOCK | REQUEST CHANGES | APPROVE

### Critical
- [Critical] src/api/orders.ts:42 — missing ownership check
  impact: any authenticated user can update another user's order
  remedy: authorize(ctx.userId === order.userId)
  flagged by: security, backend

### High
...

### Medium / Low / Nitpick
...