benchmark-fp-fn-audit

Audit React Doctor diagnostic accuracy against benchmark corpora for false positives and negatives.

14.3k|455|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/millionco/react-doctor --skill benchmark-fp-fn-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark-fp-fn-audit
Source: https://github.com/millionco/react-doctor/tree/main/.agents/skills/benchmark-fp-fn-audit
Command: npx skills add https://github.com/millionco/react-doctor --skill benchmark-fp-fn-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of verifying the accuracy of React Doctor's automated code diagnostics by performing a rigorous, evidence-backed audit against established benchmark corpora.

Core Features & Use Cases

  • Diagnostic Auditing: Systematically identifies false positives, false negatives, and taxonomy gaps in React Doctor's rule engine.
  • Evidence-Based Reporting: Generates structured audit artifacts including JSONL records and TSV distributions for high-impact rule clusters.
  • Use Case: Use this skill when you need to validate the reliability of React Doctor's findings after a new rule release or when investigating discrepancies between model-suggested patches and actual codebase health.

Quick Start

Use the benchmark-fp-fn-audit skill to perform a second adversarial pass over the current React Doctor benchmark findings.

Frequently Asked Questions about benchmark-fp-fn-audit

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

FAQPage Schema
How do I audit React code diagnostics for false positives and false negatives?

To audit React code diagnostics, compare tool output against a consolidated benchmark corpus of React codebases. This systematically identifies false positives, false negatives, and taxonomy gaps by inspecting verifier logs, patch files, and test results to produce validated audit artifacts.

What is React diagnostic accuracy benchmarking and when do I need it?

React diagnostic accuracy benchmarking verifies automated code findings against established benchmark corpora. You need it after a new diagnostic rule release or when investigating discrepancies between model-suggested patches and actual codebase health.

Can I evaluate diagnostic rule performance across specific React categories like state management and accessibility?

Yes, you can evaluate diagnostic rule performance across categories like state management, performance, and accessibility. The audit systematically compares tool output against benchmark corpora to identify rule performance gaps within these specific taxonomy clusters.

What's the best way to validate React code analysis findings after a new rule release?

The best way to validate React code analysis findings is performing a rigorous, evidence-backed audit against established benchmark corpora. This generates structured audit artifacts including JSONL records and TSV distributions for high-impact rule clusters to confirm rule engine accuracy.

What evidence artifacts does a React diagnostic audit generate?

A React diagnostic audit generates structured evidence-based reporting artifacts including JSONL records and TSV distributions for high-impact rule clusters. These artifacts validate rule engine accuracy by documenting false positives, false negatives, and taxonomy gaps found during inspection.