review-validate

Validate reported bugs with parallel sub-agents and surface tests.

11|Updated Sep 5, 2025
One-click install
npx skills add https://github.com/thrawn01/claude-dotfiles --skill review-validate-thrawn01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-validate
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/review-validate
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill review-validate-thrawn01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate reported bugs and issues by leveraging sub-agents to confirm their existence and severity.

Core Features & Use Cases

  • Validate each issue by spawning per-issue sub-agents in parallel to determine reality.
  • For each confirmed issue, generate surface tests proving the bug and present a structured findings report for review before fixes.
  • Use this skill when you need to verify bugs, test hypotheses, and safely plan fixes.

Quick Start

Run the review-validate workflow on your detected issues to obtain a findings report before applying any fixes.

Frequently Asked Questions about review-validate

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

FAQPage Schema
How do I validate reported bugs before applying code fixes?

Validate reported bugs by spawning parallel sub-agents to confirm their existence and severity, then generating surface tests and a structured findings report to guide safe fixes before updating code.

What is the best way to verify software bug hypotheses automatically?

Verify software bug hypotheses by running parallel sub-agents per issue to determine reality, followed by generating surface tests that prove the bug and present a structured findings report for review.

How do I generate surface tests for confirmed code review issues?

Generate surface tests for confirmed code review issues by using a workflow that coordinates parallel sub-agents to verify each issue, then automatically creates tests proving the bug for a findings report.

Can I run multiple bug validations in parallel during code review?

Yes, you can run multiple bug validations in parallel during code review by spawning per-issue sub-agents that independently confirm the reality of each reported issue before generating tests and findings.

Why should I use sub-agents for bug validation instead of manual testing?

Sub-agents for bug validation provide parallel verification of multiple issues, ensuring verifiable changes through surface testing and a structured findings workflow before any code updates are applied.

Do I need a findings report before fixing software bugs?

A findings report provides a structured review of confirmed issues and surface tests before fixes, ensuring verifiable changes and safe code updates rather than applying patches blindly.