independent-review

Orchestrates independent document and code reviews via a clean-context subagent on a different model.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/rombel00/game-processes --skill independent-review-rombel00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: independent-review
Source: https://github.com/rombel00/game-processes/tree/main/plugins/process-core/skills/independent-review
Command: npx skills add https://github.com/rombel00/game-processes --skill independent-review-rombel00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the same AI session that made a decision also reviews it, the review inherits the author's blind spots and defends its own reasoning. This Skill removes that bias by delegating the review to a separate subagent with a clean context and a different model, so artifacts claiming to be "done" get a genuinely independent check. ## Core Features & Use Cases - Clean-context review: The reviewer subagent receives only file paths, never a summary of why decisions were made, eliminating confirmation bias. - Different-model verification: The subagent runs on a model different from the current session, since blind spots are embedded in model weights, not just context. - Structured findings: Findings use severity labels (critical / discuss / non-blocking), a maturity score given before conclusions, and a JSON verdict of approved, rework, or blocked. - Use Case: A product document or code slice has grown large and its owner doubts it. The Skill identifies the review object (via git diff against the task_spec baseline), assembles relevant context files from the artifact registry, launches the subagent, and delivers the verdict unfiltered to the owner. ## Quick Start Ask the assistant to run an independent review of the document or code you just finished before marking it as done.

Frequently Asked Questions about independent-review

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

FAQPage Schema
How do I get an unbiased code review from an AI?▼

Delegate the review to a separate subagent with a clean context that never sees why decisions were made, and run it on a different model than the one that wrote the code. This removes both conversational bias and model-specific blind spots.

When should I run an independent review instead of a phase gate reviewer?▼

Use it for artifacts that have no dedicated gate: disputed decisions, overgrown documents, or code sections you doubt. If a phase has its own gate reviewer defined in the process map, that reviewer runs instead.

Why must the reviewer use a different model?▼

Blind spots are embedded in model weights, not only in context. A model reviewing its own output reproduces the same tendencies even with a fresh context, so a different model is required for genuine independence.

Can the review findings be applied automatically?▼

No. The review is input for the owner's decision, not a command to execute. The orchestrator delivers the verdict unfiltered and never applies fixes itself, even when the reviewer is correct.

What are the limitations of subagent-based independent review?▼

It does not replace live testing of working functionality; for implemented code it complements rather than replaces execution checks. It also costs more per run, so it should not fire on every draft.