What problem does it solve? Finished work reviewed only by its author carries the author's blind spots: unrequested additions, silently dropped requirements, and weakened tests can slip through. This Skill routes completed work to a fresh, read-only reviewer — preferably from a different model provider — so defects are caught before shipping. ## Core Features & Use Cases - Independent review modes: Prefers a cross-provider independent reviewer and falls back to a fresh same-provider agent with zero inherited context, always labelling the mode honestly. - Mandatory scope-fidelity checks: Every round verifies unrequested additions, unrequested removals, and removed or weakened tests against the original requirements. - Structured findings and convergence: Findings carry severity, evidence, and an evidence tier; a tracked ledger drives fix/push-back/defer decisions until an explicit VERDICT: no-issues on the final state. - Use Case: Before opening a PR for a payment-processing change, run a double-check so a cold-context reviewer attacks the riskiest claims, diffs the test files, and confirms nothing outside the original scope was added or removed. ## Quick Start Ask the agent to double-check the finished implementation against the original requirements before opening the pull request.
