Agent skill · Frontend

run-parity

Compare React Doctor diagnostics for a GitHub pull request (PR) with Daytona. Use when asked to run parity, check a PR for diagnostic regressions, compare a PR with its base, or report added and removed diagnostics.

Million Software, Inc.14,162★ · +123/wk · 1 repos on radarProfile →
claude-codeships scriptsNOASSERTION
Install
npx skills add millionco/react-doctor --skill run-parity --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 17
SKILL.md size: 16 KB
Bundled scripts: yes
Path: .agents/skills/run-parity/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 14,264 · +102 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Run pull request parity Run the pull request base and head against the same repository commits. Write deterministic newline-delimited JSON (NDJSON) artifacts and compare them. ## Prepare the run Require `DAYTONA_API_KEY`, authenticated `gh`, and a pushed pull request head. Do not push changes without permission. Use `ni` and `nr` in this repository. Resolve the pull request: ```sh gh pr view <pr-number-or-url> \ --json number,url,baseRefOid,headRefOid,headRepository,headRepositoryOwner ``` Derive the base repository from the pull request URL. Derive the head repository from `headRepositoryOwner.login` and `headRepository.name`. Use the returned commit hashes, not branch names. Create `tmp/parity-pr-<number>-<head-short-sha>` and preserve it after the run. Run `ni` before evaluation. ## Run both revisions Run from `packages/evals`. The default corpus contains the 2,000 highest-ranked repositories, and the initial concurrency is 200. Sandbox creation is capped at 20 to avoid overloading Daytona. The evaluator cleans up resources and retries failed projects at concurrency 50, then 10. ```sh nr --silent eval \ --react-doctor-repository <base-repository-url> \ --react-doctor-ref <base

What's inside
Steps it walks through
  1. Prepare the run
  2. Run both revisions
  3. Compare results
  4. Report results
Ships with 16 files
  • agents/openai.yaml
  • scripts/baseline-cache-provenance.mjs
  • scripts/baseline-cache-provenance.test.mjs
  • scripts/build-parity-index.mjs
  • scripts/compare-parity-indexes.mjs
  • scripts/compare-parity-performance.mjs
  • scripts/compare-parity-performance.test.mjs
  • scripts/compare-parity.mjs
  • scripts/compare-parity.test.mjs
  • scripts/find-impacted-rules.mjs
  • scripts/find-impacted-rules.test.mjs
  • scripts/parity-index.test.mjs
  • scripts/validate-parity-input.jq
  • scripts/validate-parity-input.test.mjs
  • scripts/verify-matrix-artifact.mjs
  • scripts/verify-matrix-artifact.test.mjs
Commands it runs
gh pr view <pr-number-or-url> \
nr --silent eval \
node .agents/skills/run-parity/scripts/baseline-cache-provenance.mjs create \
cd packages/evals
nr --silent matrix-corpus-identity <absolute-corpus-manifest-path>
nr --silent source-hash
node .agents/skills/run-parity/scripts/verify-matrix-artifact.mjs \
Incremental treatment
node .agents/skills/run-parity/scripts/compare-parity.mjs \
Full treatment
More from react-doctor
All skills →
About this skill
What does the run-parity skill do?

Compare React Doctor diagnostics for a GitHub pull request (PR) with Daytona. Use when asked to run parity, check a PR for diagnostic regressions, compare a PR with its base, or report added and removed diagnostics.

How do I install it?

Run `npx skills add millionco/react-doctor --skill run-parity --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From millionco/react-doctor, a repository with 14,264 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going