メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orchestrate the Rust compiler port end-to-end. Discovers the current frontier, fixes failing passes, ports new passes, reviews, and commits in a loop.
Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.
Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.
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.
Use when you need to update a plan document with deep research across all compiler passes. Launches parallel subagents to analyze how a topic affects every compiler phase, then consolidates findings into the plan doc.
Show the status of all Rust port plan documents and recent related commits. Use when you need to understand what's been done vs what remains.
| name | compiler-commit |
| description | 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. |
Verify and commit compiler changes with the correct convention.
Arguments:
-- (e.g., Fix aliasing bug -- aliasing)Run /compiler-verify first (with test pattern if provided after --). Stop on any failure.
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.
Detect commit prefix from changed files:
compiler/crates/ changed: use [rust-compiler][compiler]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:
# Status section with the results (use the frontier, per-pass counts, and pass/fail totals)## YYYYMMDD-HHMMSS log entry noting the commit and what changedStage 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 ..
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.
/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