rch

# RCH — Remote Compilation Helper `rch` transparently offloads compilation commands to remote workers via a Claude Code PreToolUse hook. The daemon picks the fastest healthy worker, rsync's the workspace, runs the build, syncs artifacts back, and exits with the worker's exit code. This skill is the operational layer agents use when something about that pipeline isn't working — and the much more common case where it *thinks* it's working but is silently falling back to local execution. The skill is built around a single principle: **self-resolve before asking the human.** Every recovery path here is one the agent can run on its own. **Don't re-learn the command surface here.** `rch --help`, `rch doctor`, and the machine surfaces (`--json`, `--schema`, `--help-json`, `--capabilities` — see [MACHINE_INTROSPECTION.md](references/MACHINE_INTROSPECTION.md)) self-describe every subcommand, flag, and env var. Env-var knobs and config precedence: [CONFIGURATION.md](references/CONFIGURATION.md). This skill carries the triage doctrine and recovery playbook routing. Tested against rch v1.0.18; concepts apply to v1.0.16+. --- ## Read This First When a build feels slow, run **one** thing: ```bash RCH_VISIBILITY=verbose <your-command> 2>&1 | grep -E '^\[RCH\]' ``` The summary line is a contract: | Pattern | What to do | |---|---| | `[RCH] remote <worker> (...)` | Healthy. Done. | | `[RCH] remote <worker> failed [RCH-Exxx] ...` | Real build/env failure. See [ERROR_CODES.md](referen...