Index of every page on this site: llms.txt
All skills
react avatar

/compiler-verify

@76baa3b official
by reactreact/react252k stars
51,625
Run it yourself

Use when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.

  • 1 file
  • 2 KB
  • Updated 5 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/react/react/compiler-verify

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈44 tokens for metadata: the name and description. ≈472 when used: this file.

Description uses 2.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈176 characters, or 2.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Compiler Verify

Run all verification steps for compiler changes.

Arguments:

  • $ARGUMENTS: Optional test pattern for yarn snap -p <pattern>

Instructions

  1. Detect what changed by running git diff --name-only HEAD (or vs the base branch). Categorize changes:

    • TS changes: files in compiler/packages/
    • Rust changes: files in compiler/crates/
    • Both: run all checks
  2. If TS changed, run these sequentially (stop on failure):

    • yarn snap (or yarn snap -p <pattern> if a pattern was provided) — compiler tests
    • yarn test — test full compiler
    • yarn workspace babel-plugin-react-compiler lint — lint compiler source
  3. If Rust changed, run these sequentially (stop on failure):

    • bash compiler/scripts/test-babel-ast.sh — Babel AST round-trip tests
    • bash compiler/scripts/test-rust-port.sh — full Rust port test suite (compares Rust vs TS compiler output across all passes; must have 0 failures — do not regress)
    • yarn snap --rust — end-to-end snap tests using the Rust compiler (compares compiled output and logger events against .expect.md fixtures; use yarn snap --rust -p <pattern> for focused checks)
  4. Always run (from the repo root):

    • yarn prettier-all — format all changed files
  5. If implementing a plan doc, check:

    • Plan doc has no unaddressed "Remaining Work" items
    • Plan doc status is updated to reflect current state
  6. Report results: list each step as passed/failed. On failure, stop and show the error with suggested fixes.

Common Mistakes

  • Running yarn snap without -p is fine for full verification, but slow. Use -p for focused checks.
  • Running prettier from compiler/ — must run from the repo root.
  • Forgetting Rust tests — if you touched .rs files, always run the round-trip test and yarn snap --rust.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 76baa3b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 5 months ago

README badge

README badge for react/react/compiler-verify

Runs all verification steps (tests, lint, format) for React Compiler changes, detecting whether TypeScript or Rust code changed and executing the appropriate checks. Includes Babel AST round-trip tests, Rust port validation, snapshot tests, and code formatting for the facebook/react compiler monorepo.

Generated from the current SKILL.md.

Does this skill work for TypeScript and Rust changes separately?
Yes. It detects which files changed (TS in compiler/packages/ or Rust in compiler/crates/) and runs the appropriate test suites for each, or all checks if both changed.
What happens if a test fails?
The skill stops at the first failure and reports the error with suggested fixes rather than continuing through the remaining checks.
Can I run focused tests on a subset of files?
Yes. Pass a test pattern as an argument to use yarn snap -p <pattern> for faster, focused verification instead of the full suite.
Does this skill handle code formatting?
Yes. It always runs yarn prettier-all from the repo root to format all changed files.
What is the Rust port test suite checking for?
It compares Rust compiler output against the TypeScript version across all passes and requires zero failures to ensure no regressions.

Generated from the current SKILL.md. These answers refresh after source changes.