independent-review

Delegates a read-only code review to a fresh subagent and verifies each finding against the source.

1|Updated Dec 18, 2009
One-click install
npx skills add https://github.com/thurn/dotfiles --skill independent-review-thurn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: independent-review
Source: https://github.com/thurn/dotfiles/tree/main/.llms/skills/independent-review
Command: npx skills add https://github.com/thurn/dotfiles --skill independent-review-thurn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing a nontrivial code change, the author is often blind to defects in their own reasoning. This Skill obtains a genuinely independent second opinion from a fresh subagent, then forces every reported finding to be verified against the real code before any fix is made. ## Core Features & Use Cases - Independent subagent review: Spawns a fresh gpt-5.6-sol subagent with no inherited context to review the diff read-only, reporting only actionable bugs, architectural problems, brittle tests, and missing coverage. - Finding verification workflow: Each finding is treated as a claim to be proven or rejected against the actual code, so fixes are made only for confirmed defects. - Validation sequencing: Runs cheap focused checks before review and defers expensive aggregate validation until after findings are resolved, avoiding wasted validation runs. - Use Case: After implementing a refactor that moves state handling between modules, run this Skill to get an unbiased review of the diff, confirm or reject each reported issue, fix the real ones, and report the disposition of every finding. ## Quick Start Ask the assistant to run an independent review of the change you just finished before declaring it 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 independent code review of my change?▼

Run this Skill after finishing a nontrivial change. It spawns a fresh gpt-5.6-sol subagent with no inherited context to review the diff read-only, then verifies each finding against the real code before fixing anything.

When should I run an independent review versus skipping it?▼

Use it for nontrivial changes: new behavior, logic-heavy bug fixes, refactors, or anything touching state, ordering, persistence, or contracts. Skip it for typo fixes, comment edits, config tweaks, and mechanical renames.

Does the reviewing subagent fix the issues it finds?▼

No. The reviewer is strictly read-only and never edits files. The main agent verifies each finding against the actual code and implements fixes only for confirmed defects.

Can I run multiple independent reviews in one session?▼

No. The Skill runs at most one completed review per session, including follow-up tasks and reviewer-driven fixes. An additional pass happens only when the user explicitly requests another review.

What kinds of findings does the independent reviewer report?▼

It reports only actionable correctness bugs, architectural problems, brittle tests, missing coverage for changed behavior, and duplication likely to diverge. Style, naming, aesthetic, and security observations are explicitly out of scope and dropped.

Should I run the full test suite before requesting the review?▼

No. Run only cheap focused checks that exercise the changed behavior before review. Expensive aggregate or release validation is deferred until after findings are resolved so it runs once against the final source.