Install any skill in seconds. Free to start, no credit card required.
Get Started Free →react/compiler-verify
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.
Passed 13 of 17 test cases with the skill, and 6 of 17 without it.
and 6 more in the full report
9 fixed8 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I modified a JSX transforms pass in `compiler/packages/` and want to run snapshot tests specifically for the 'inline-jsx' pattern without running all snapshot fixtures. What exact command should I run?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies yarn snap -p inline-jsx. | Missed | Passed |
The instructions your model reads when the skill loads.
Run all verification steps for compiler changes.
Arguments:
yarn snap -p <pattern>Detect what changed by running git diff --name-only HEAD (or vs the base branch).
Categorize changes:
compiler/packages/compiler/crates/If TS changed, run these sequentially (stop on failure):
yarn snap (or yarn snap -p <pattern> if a pattern was provided) — compiler testsyarn test — test full compileryarn workspace babel-plugin-react-compiler lint — lint compiler sourceIf Rust changed, run these sequentially (stop on failure):
bash compiler/scripts/test-babel-ast.sh — Babel AST round-trip testsbash 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)Always run (from the repo root):
yarn prettier-all — format all changed filesIf implementing a plan doc, check:
Report results: list each step as passed/failed. On failure, stop and show the error with suggested fixes.
yarn snap without -p is fine for full verification, but slow. Use -p for focused checks..rs files, always run the round-trip test and yarn snap --rust.test cases passed, vs 6 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.