adjudicate-review

Verify review findings against source material before applying fixes.

1.5k|3.0k|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/pedrohcgs/claude-code-my-workflow --skill adjudicate-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adjudicate-review
Source: https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/adjudicate-review
Command: npx skills add https://github.com/pedrohcgs/claude-code-my-workflow --skill adjudicate-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewers — especially AI models — produce confident, specific findings that are wrong at a meaningful rate, and blindly applying their suggested fixes can break correct work. This Skill turns incoming review comments into evidence-backed decisions instead of unverified edits.

Core Features & Use Cases

  • Finding triage and verification: Classify each finding by type and severity, then confirm, refute, or partially confirm it against the actual source with line-level evidence.
  • Mechanical checks over opinion: Run computable checks — grep symbols, resolve cross-references, execute consuming code — before trusting reviewer confidence.
  • Poisoned-fix detection: Evaluate the proposed fix, not just the finding, to avoid introducing real defects while addressing cosmetic ones.
  • Use Case: You receive a 40-item AI referee report on a research paper. Use this Skill to verify each claim against the manuscript, batch the confirmed fixes, refute misreads with cited text, and add signposts where reviewers stumbled.

Quick Start

Adjudicate the attached referee report against my paper, verifying each finding before making any changes.

Frequently Asked Questions about adjudicate-review

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

FAQPage Schema
How do I handle AI-generated code review comments?

Treat each AI review comment as a candidate hypothesis, not a verdict. Verify it against the actual source with line-level evidence, run mechanical checks where possible, and only apply fixes for confirmed findings.

How to respond to a referee report on a research paper?

Triage findings by type and severity, verify each against the manuscript, then batch confirmed fixes and rebuild. Refuted findings should be answered with the specific text that refutes them, and owner-level decisions escalated rather than decided unilaterally.

Can two AI reviewers agreeing confirm a defect?

No. Models share failure modes and converge on the same wrong answer, so agreement is weak evidence. Independent computation — running the code, grepping the symbol, resolving the reference — is what confirms a finding.

Why do AI reviewers report false findings on correct work?

The dominant cause is remoteness: the claim is correct, but its justification sits elsewhere — a standing assumption, an earlier paragraph, or an imported premise. Adding local signposts where reviewers stumbled reduces repeat misreads.

When should I stop adjudicating review rounds?

Stop when a confirmation pass returns no new confirmed defects — only held items and taste. When a round yields mostly refutations and artifacts, further rounds cost more to adjudicate than they return.