
Compiler Commit
FreeVerify and commit compiler changes with ease.
Free · Opens the source repo
What Compiler Commit does
The Compiler Commit skill is designed for developers who need to ensure that their compiler-related changes are correctly verified and committed following a specific convention. This skill automates the process of running tests, linting code, and formatting before committing changes, which helps maintain code quality and consistency across projects. By using this skill, developers can streamline their workflow, reduce the chances of errors, and adhere to the project's commit message standards.
To use the skill, you start by running the /compiler-verify command, which checks for any issues in the code changes. If any tests fail, the process stops, allowing you to address the problems before proceeding. After verification, the /compiler-review command is executed to analyze uncommitted changes, providing feedback and halting the commit process if any issues are detected. This ensures that only well-reviewed changes are committed to the repository.
The skill intelligently determines the appropriate commit prefix based on the files that have changed, using [rust-compiler] for Rust-related changes and [compiler] for others. It also updates the orchestrator log if necessary, capturing the results of the Rust tests in a structured format. This level of detail aids in tracking changes and understanding the impact of commits over time.
Overall, the Compiler Commit skill is ideal for developers working with compiler codebases, particularly those using Rust. It simplifies the commit process while ensuring that all necessary checks are performed, making it a valuable addition to any developer's toolkit.
When to use it
Use this skill when making changes to compiler-related code that require verification and proper commit formatting.
When not to use it
This skill may not be suitable for general-purpose commits unrelated to compiler changes, nor for projects that do not follow the specified commit conventions.
What you can build with it
Fixing a Bug in Compiler Code
Use `/compiler-commit Fix aliasing bug in optional chains` to verify and commit bug fixes in the compiler.
Implementing New Features
Run `/compiler-commit Implement scope tree types -- round_trip` to add new features while ensuring all tests pass.
Maintaining Commit Standards
Utilize this skill to ensure all your compiler-related commits follow the project's naming conventions and quality checks.
How to install Compiler Commit
View source1. Install with the skills CLI
npx skills add react/react/compiler-commit --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by reactCompiler 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
-
Run
/compiler-verifyfirst (with test pattern if provided after--). Stop on any failure. -
Run
/compiler-reviewon 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. -
Detect commit prefix from changed files:
- If any files in
compiler/crates/changed: use[rust-compiler] - Otherwise: use
[compiler]
- If any files in
-
Update orchestrator log: If
compiler/docs/rust-port/rust-port-orchestrator-log.mdexists and the commit includes Rust changes (compiler/crates/):Run
test-rust-portwith--jsonto get machine-readable results:bash compiler/scripts/test-rust-port.sh --json 2>/dev/nullThis outputs a JSON object with fields:
pass,autoDetected,total,passed,failed,frontier,perPass,failures.Then update the orchestrator log:
- Update the
# Statussection with the results (use the frontier, per-pass counts, and pass/fail totals) - Add a
## YYYYMMDD-HHMMSSlog entry noting the commit and what changed
- Update the
-
Stage files — stage only the relevant changed files by name (including the orchestrator log if updated in step 4). Do NOT use
git add -Aorgit add .. -
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.
-
Commit using a heredoc for the message:
git commit -m "$(cat <<'EOF' [rust-compiler] Title here Summary here. EOF )" -
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
Frequently asked questions about Compiler Commit
Similar skills
Release Candidate Preparation
Streamline your OpenAI Agents release process.
Gitmoji
Generate expressive commit messages with emojis.
GitHub Release
Automate your GitHub library release process effortlessly.
Commit Message Storyteller
Generate meaningful commit messages from your git diffs.
Author Contributions
Trace author contributions across branches in Git.
Implementation Kickoff
Streamline your code implementation process with ease.
