skilld
All skills
facebook avatar

/compiler-commit

@03e7755 official
by Metafacebook/react251k stars
51,417

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.

Requires /compiler-verify /compiler-review
  • 1 file
  • 2.4 KB
  • Updated 4 months ago
  • GitHub

Ask your Agent

Use this Skill: https://skilld.dev/gh/facebook/react/compiler-commit

This session only. Nothing lands on disk.

SKILL.md

≈48 tokens always: the name and description. ≈556 when used: this file.

Compiler Commit

Verify and commit compiler changes with the correct convention.

Arguments:

  • $ARGUMENTS: Commit title (required). Optionally a test pattern after -- (e.g., Fix aliasing bug -- aliasing)

Instructions

  1. Run /compiler-verify first (with test pattern if provided after --). Stop on any failure.

  2. Run /compiler-review on the uncommitted changes. Report the findings to the user. If any issues are found, stop and do NOT commit — let the user decide how to proceed.

  3. Detect commit prefix from changed files:

    • If any files in compiler/crates/ changed: use [rust-compiler]
    • Otherwise: use [compiler]

  4. Update orchestrator log: If compiler/docs/rust-port/rust-port-orchestrator-log.md exists and the commit includes Rust changes (compiler/crates/):

    Run test-rust-port with --json to get machine-readable results:

    bash compiler/scripts/test-rust-port.sh --json 2>/dev/null

    This outputs a JSON object with fields: pass, autoDetected, total, passed, failed, frontier, perPass, failures.

    Then update the orchestrator log:

    • Update the # Status section with the results (use the frontier, per-pass counts, and pass/fail totals)
    • Add a ## YYYYMMDD-HHMMSS log entry noting the commit and what changed

  5. Stage files — stage only the relevant changed files by name (including the orchestrator log if updated in step 4). Do NOT use git add -A or git add ..

  6. Compose commit message:

    [prefix] <title>

<summary of what changed and why, 1-3 sentences>

    The title comes from $ARGUMENTS. Write the summary yourself based on the actual changes.

  7. Commit using a heredoc for the message:

    git commit -m "$(cat <<'EOF'
[rust-compiler] Title here

Summary here.
EOF
)"

  8. Do NOT push unless the user explicitly asks.

Examples

  • /compiler-commit Fix aliasing bug in optional chains — runs full verify, commits as [compiler] Fix aliasing bug in optional chains
  • /compiler-commit Implement scope tree types -- round_trip — runs verify with -p round_trip, commits as [rust-compiler] Implement scope tree types

Source: SKILL.md on GitHub

Third-party checks

No third-party reports yet.

Provenance

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

Last checked against GitHub yesterday.

Activeupdated 4 months ago

Topics

README badge

README badge for facebook/react/compiler-commit

What it does

Runs compiler tests, lint, and format checks, then commits with [compiler] or [rust-compiler] prefix based on which files changed. Targets the React compiler repository workflow and optionally updates a Rust port orchestrator log when Rust crate changes are detected.

Generated from the current SKILL.md.

Frequently asked

What does this skill do?
This skill verifies compiler changes by running tests, lint, and format checks, then commits with the [compiler] or [rust-compiler] prefix based on which files changed. It also updates the Rust port orchestrator log if applicable.
How does it decide between [compiler] and [rust-compiler] prefixes?
If any files in compiler/crates/ changed, it uses [rust-compiler]. Otherwise it uses [compiler].
What happens if verification or review fails?
The skill stops and does not commit. You must resolve the issues before retrying.
Can I run tests on a specific pattern?
Yes. Pass the test pattern after `--` in the commit title argument, e.g. `Fix aliasing bug -- aliasing`.
Does this push the commit automatically?
No. The skill commits locally but does not push unless you explicitly ask.

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