compiler-commit

Verify compiler changes and commit with the correct prefix convention.

248k|51.3k|Updated May 24, 2013
One-click install
npx skills add https://github.com/facebook/react --skill compiler-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compiler-commit
Source: https://github.com/facebook/react/tree/main/compiler/.claude/skills/compiler-commit
Command: npx skills add https://github.com/facebook/react --skill compiler-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually committing compiler changes requires running multiple verification steps, choosing the right commit prefix, and updating tracking logs, which is error-prone and inconsistent across contributors.

Core Features & Use Cases

  • Automated Verification Pipeline: Runs compiler tests, lint, and format checks before allowing a commit, preventing broken code from entering the repository.
  • Smart Prefix Detection: Automatically selects [rust-compiler] or [compiler] based on whether files in compiler/crates/ were modified.
  • Orchestrator Log Maintenance: Updates the Rust port orchestrator log with test results when Rust changes are included in the commit.
  • Use Case: A contributor finishes implementing a new aliasing optimization in the React compiler. They invoke this skill with the commit title, and it runs all verification, reviews the diff, updates the tracking log, and creates a properly formatted commit message.

Quick Start

Use the compiler-commit skill to verify my uncommitted changes and commit them with the appropriate prefix.

Frequently Asked Questions about compiler-commit

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

FAQPage Schema
How do I commit changes to the React compiler with the correct prefix?▼

Use the compiler-commit skill which automatically detects whether changes are in compiler/crates/ to apply the [rust-compiler] prefix, or [compiler] for other compiler files. It runs verification steps before staging and committing.

What verification steps run before a compiler commit?▼

The skill runs compiler-verify (tests, lint, format) and compiler-review on uncommitted changes. If any verification fails or review issues are found, the commit is aborted and the user is notified.

Can I run a specific test pattern when committing compiler changes?▼

Yes, pass the test pattern after -- in the arguments, for example: /compiler-commit Fix aliasing bug -- aliasing. The pattern is forwarded to the verify step to filter which tests run.

Why does the commit prefix change between [compiler] and [rust-compiler]?▼

The prefix is determined by file paths: changes inside compiler/crates/ indicate Rust port work and use [rust-compiler], while other compiler changes use [compiler]. This convention tracks the Rust migration progress separately.

Does the skill push commits to the remote repository?▼

No, the skill only creates the local commit. Pushing requires an explicit user request to avoid accidentally publishing unverified or unreviewed changes.