compiler-orchestrator

Orchestrate the Rust compiler port end-to-end through a continuous fix-and-port loop.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually porting the React compiler from TypeScript to Rust across 49 sequential passes is error-prone and slow. This Skill automates the discovery of the current frontier, fixes failing passes, ports new ones, reviews changes, and commits progress in a continuous loop.

Core Features & Use Cases

  • Frontier Discovery: Runs test-rust-port.sh --json to identify the earliest failing pass and determine whether to enter FIX or PORT mode.
  • Parallel Diagnosis: Launches review and analysis subagents in parallel to diagnose test failures before delegating fixes.
  • Delegated Implementation: Routes all code reading, debugging, porting, and committing to subagents, keeping the main context as a pure orchestration loop.
  • Use Case: Drive the React compiler Rust port forward by repeatedly discovering the frontier pass, fixing or porting it via subagents, reviewing the diff, and committing with the [rust-compiler] prefix until all 49 passes are clean.

Quick Start

Run the compiler orchestrator skill to discover the current frontier and continue porting the Rust compiler passes.

Frequently Asked Questions about compiler-orchestrator

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

FAQPage Schema
How do I port the React compiler from TypeScript to Rust?

Use the compiler-orchestrator skill to drive the port automatically. It discovers the frontier pass via test-rust-port.sh, delegates porting to subagents, and commits each pass with the [rust-compiler] prefix until all 49 passes are clean.

What is the pass order for the React compiler pipeline?

The pipeline runs 49 passes in order: HIR passes (1-31) including PruneMaybeThrows, SSA, InferTypes, and BuildReactiveScopeTerminalsHIR, then reactive passes (32-47) like BuildReactiveFunction and RenameVariables, followed by debug validators and Codegen.

How does the orchestrator decide between FIX and PORT mode?

FIX mode activates when the frontier is a ported pass with test failures. PORT mode activates when the frontier is the next unported pass. The orchestrator reads test-rust-port.sh --json output to determine the frontier and mode automatically.

Why does the main context delegate all work to subagents?

The main context is reserved for orchestration only: parsing subagent results, updating the orchestrator log, printing status, and launching the next subagent. All code reading, debugging, fixing, porting, reviewing, and committing happens in subagents to keep the loop efficient.

Can the orchestrator handle conditional passes like DropManualMemoization?

Yes. Conditional passes (3, 13, 19, 21, 22) are noted when delegating to subagents. Special cases like the second PruneMaybeThrows call (#15) and outlineJSX between #20 and #21 have explicit handling instructions in the orchestrator.