impartial-review

Dispatches five fresh-context reviewer subagents to audit code diffs across categorized finding buckets.

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/ryanportfolio/threejs-interview-test --skill impartial-review-ryanportfolio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: impartial-review
Source: https://github.com/ryanportfolio/threejs-interview-test/tree/main/.claude/skills/impartial-review
Command: npx skills add https://github.com/ryanportfolio/threejs-interview-test --skill impartial-review-ryanportfolio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews performed in the same session that wrote the code suffer from author bias, causing real bugs and missed changes to slip through. This Skill structurally removes that bias by delegating review to fresh-context subagents that never saw the conversation that produced the code. ## Core Features & Use Cases - Five-bucket parallel review: Dispatches concurrent reviewer subagents covering correctness, data flow, performance/security/observability, missed changes, and project-rule violations. - Coverage-then-precision pipeline: Subagents over-report findings with severity and confidence tags; the main session verifies, deduplicates, and severity-orders every finding before presenting it. - Multi-runtime support: Works from Claude Code via Agent tool calls or from Codex via parallel codex exec processes, with an opt-in strict maintainability rubric for deep structural audits. - Use Case: After landing a large feature branch, ask for an impartial review of the PR diff and receive a verified, severity-ranked findings list with blocking issues, dismissed false positives, and a merge recommendation. ## Quick Start Ask the assistant to impartially review the most recent commit or the current uncommitted changes using fresh reviewer subagents.

Frequently Asked Questions about impartial-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an unbiased code review of my recent changes?▼

Request an impartial review of your diff, and the Skill dispatches five fresh-context reviewer subagents that never saw the code-writing conversation. Each covers a distinct bucket: correctness, data flow, performance/security, missed changes, and project-rule violations.

How does multi-agent code review work in Claude Code or Codex?▼

In Claude Code, five Agent tool calls run concurrently with general-purpose subagents. In Codex, five `codex exec` processes run in parallel with read-only sandboxes, each writing its report to a separate output file.

When should I use inline review instead of dispatching subagents?▼

Use inline review only for tiny diffs under roughly 50 changed lines in a single file with no schema, auth, or cache code. Everything else defaults to the five-subagent dispatch, since missed bugs cost more than the extra tokens.

What is the strict or thermo-nuclear review mode?▼

Strict mode loads an additional maintainability rubric appended to the missed-changes reviewer. It raises the approval bar with presumptive blockers like the 1000-line file rule, spaghetti branching growth, and missed structural simplification opportunities.

Why did a reviewer report a finding that turned out to be wrong?▼

Subagents deliberately over-report for coverage, tagging each finding with confidence. The main session verifies every finding with real grep and file reads before surfacing it, and refuted findings appear in a Dismissed section with reasons.