validate-code

Dispatches parallel review-code subagents against a code diff and summarizes results.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/mikestopcontinues/agent-skills --skill validate-code-mikestopcontinues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-code
Source: https://github.com/mikestopcontinues/agent-skills/tree/main/claude/skills/validate-code
Command: npx skills add https://github.com/mikestopcontinues/agent-skills --skill validate-code-mikestopcontinues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multi-perspective code reviews manually is slow and error-prone. This Skill automates the fan-out of focused code reviews by resolving a code artifact to a unified diff, dispatching one review-code subagent per requested focus in parallel, and returning a consolidated summary of which review files were written and which reviewers errored. ## Core Features & Use Cases - Artifact-to-diff resolution: Accepts a .diff/.patch file, a single source file, or a directory, and derives a unified diff via git diff against the worktree base branch, with an empty-diff guard that refuses to dispatch when there is nothing to review. - Parallel focus fan-out: Dispatches one review-code subagent per focus (architecture, accuracy, dx, security, performance, etc.) in a single batch, each writing an rNN-{focus}.md review file with automatically derived sequential numbering. - Error surfacing summary: Produces a status table showing which review files landed and which reviewers errored, with an overall ok/failed headline so calling skills can decide whether to proceed. - Use Case: During plan execution, execute-plan calls this Skill with a baseline focus list of accuracy, architecture, and dx to get three independent review reports on the just-written code before merging. ## Quick Start Ask the agent to validate the code changes in the current worktree with the focuses accuracy, architecture, and dx, writing the review files into the reviews directory.

Frequently Asked Questions about validate-code

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

FAQPage Schema
How do I run parallel code reviews on a git diff?▼

Provide the artifact path (a diff file, source file, or directory) plus a focus list. The skill resolves the artifact to a unified diff via git diff against the base branch, then dispatches one review-code subagent per focus in a single parallel batch.

What inputs does an automated code review dispatcher need?▼

It needs an artifact path (a .diff/.patch file, a single source file, or a directory) and an ordered focus list such as accuracy, architecture, or dx. Optional inputs are an iteration number and a reviewDir where the rNN-{focus}.md files are written.

What happens when the diff is empty during code review?▼

The skill refuses with a clear error stating the artifact produced an empty diff against the base branch and dispatches no subagents. The error itself is returned as the summary so the calling skill can decide how to proceed.

How are review output files numbered?▼

Existing rNN-*.md files in the review directory are scanned, and the next number is max plus one, or 1 when the directory is empty. Each focus at index i gets r{next + i}-{focus}.md, so the first focus in an empty directory lands at r1-{focus}.md.

Does the code review dispatcher retry failed reviewers?▼

No. Errored, missing, or empty review files are surfaced in the summary table's status and error columns without auto-retry or auto-bypass. The overall status is failed if any reviewer errored, and the calling skill decides whether to re-dispatch or escalate.