validate-external-review

Verifies findings from external code reviews against the actual codebase and produces a structured triage report.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/nejcm/agents --skill validate-external-review-nejcm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-external-review
Source: https://github.com/nejcm/agents/tree/main/skills/validate-external-review
Command: npx skills add https://github.com/nejcm/agents --skill validate-external-review-nejcm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you receive a code review from another AI model, a review bot, or a teammate, you cannot tell which findings are real without manually checking each one against the code. This Skill cross-checks every claimed issue against the actual codebase and classifies it, so you only act on genuine problems. ## Core Features & Use Cases - Finding-by-finding verification: Parses each discrete finding (claim, file:line location, severity) and reads the referenced code to confirm or refute it. - Structured verdicts: Classifies every finding as Valid, Invalid, Partial, Already fixed, or Needs info, with quoted code evidence and reasoning. - Triage report output: Produces a grouped summary with counts per verdict and clear next-step prompts, without modifying any code. - Use Case: A review bot flags 12 issues in your pull request. Run this Skill to discover that 4 are valid bugs, 6 are misreadings of the code, and 2 were already fixed, then fix only the real ones. ## Quick Start Validate the findings in this pasted review report against my current codebase and give me a triage of which ones are real.

Frequently Asked Questions about validate-external-review

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

FAQPage Schema
How do I verify AI code review findings against my codebase?▼

Provide the review as pasted text, a file path, or a URL, and each discrete finding is checked against the referenced file and line. Every claim receives a verdict of Valid, Invalid, Partial, Already fixed, or Needs info with quoted code evidence.

How to triage review bot comments on a pull request?▼

Extract each finding with its claim, location, and severity, then verify it against the actual code. The output is a structured triage report grouping findings by verdict so you can fix only confirmed issues.

Does this skill fix the valid findings it confirms?▼

No, it never edits or modifies code unless you explicitly request it. After the triage report, it prompts you to say "fix the valid ones" if you want the confirmed issues addressed.

What happens if a finding references a file that does not exist?▼

The finding is marked Invalid rather than Needs info, since a nonexistent file means the claim cannot match the code. Needs info is reserved for cases requiring runtime behavior or external context.

When should I use code review instead of validating an external review?▼

Use a fresh code review when you want the code itself examined for issues. Use validation only when you already have a review report from another model, bot, or teammate and need its findings cross-checked.