skills.rest
millionco
millioncoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

run-parity

Compare React Doctor NDJSON diagnostic reports between pull request heads and base branches.

14.3k|455|Updated Feb 13, 2026
Search Tags:#react#diagnostics#github-actions#ci-cd#code-analysis#regression-testing
One-click install
npx skills add https://github.com/millionco/react-doctor --skill run-parity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-parity
Source: https://github.com/millionco/react-doctor/tree/main/.agents/skills/run-parity
Command: npx skills add https://github.com/millionco/react-doctor --skill run-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node:crypto, node:fs, node:path, node:readline, node:util, and includes scripts (resource) components.

What problem does it solve?

This skill automates the comparison of React Doctor diagnostics between a pull request and its base branch, ensuring that new code changes do not introduce unexpected diagnostic regressions or false positives.

Core Features & Use Cases

  • Deterministic Comparison: Runs scans against both base and head commits to generate and compare NDJSON diagnostic reports.
  • Cache-Aware Evaluation: Uses immutable provenance and caching to skip redundant scans, significantly reducing CI time and resource usage.
  • Use Case: When a developer submits a PR that modifies React Doctor rules, this skill verifies that the changes only affect the intended code paths by comparing the full diagnostic output against the baseline.

Quick Start

Use the run-parity skill to compare the diagnostics of the current pull request against its base branch and report any added or removed issues.

Frequently Asked Questions about run-parity

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

FAQPage Schema
How do I detect React diagnostic regressions in a GitHub pull request?▼

To detect React diagnostic regressions, run-parity compares NDJSON diagnostic outputs between a pull request head and its base branch to identify newly added or removed issues.

What is deterministic code analysis for CI/CD regression testing?▼

Deterministic code analysis for regression testing executes scans against base and head commits to generate comparable NDJSON reports, ensuring consistent diagnostic results across large codebases.

Does run-parity require authenticated GitHub access to compare diagnostics?▼

Yes, run-parity requires authenticated GitHub access to retrieve pull request data and execute scans across commits using Daytona sandboxes and the React Doctor CLI.

How do I reduce CI time when running React Doctor scans on large codebases?▼

You can reduce CI time by using cache-aware evaluation with immutable provenance, which skips redundant diagnostic scans across base and head branches during regression testing.

Can I use Daytona sandboxes for regression testing on React codebases?▼

Yes, Daytona sandboxes execute deterministic scans across large React codebases, generating and comparing NDJSON diagnostic report artifacts to validate pull request changes.

What are the limitations of comparing NDJSON diagnostic reports for regression testing?▼

Comparing NDJSON diagnostic reports requires the React Doctor CLI and authenticated GitHub access, meaning regression testing cannot run without these dependencies and valid pull request base branches.

Related Skills

Explore More Software Engineering Skills→
tobihagemanntobihagemann
399

fetch-pr-comments

Fetch and summarize unresolved GitHub PR review comments via GraphQL.

Community
Intermediate
bidahbidah
28

github-actions

Generate GitHub Actions workflows for React Native iOS and Android artifact builds.

Community
Advanced
QredenceQredence
51

sandbox-execution

Execute Python code in Daytona sandboxes with durable volume persistence.

Official
Intermediate
chriswesttchriswestt

ship

Merge the base branch, run tests, and create a pull request.

Community
Advanced