remote-compilation-helper-setup

Setting up remote build workers requires configuring the workers.toml file with total_slots, priority, and tags, then installing a PreToolUse hook to route compilation commands. This skill automates that worker configuration and validates daemon operation across environments.

Remote compilation helper setup requires Rust nightly, rsync, and zstd to be installed on your machines. You also need to integrate SSH keys and configure the daemon prerequisites before validating the setup using the rch doctor diagnostics workflow.

Remote build hook failures often stem from incorrect installation or missing daemon prerequisites. You can diagnose these hook issues by verifying SSH access, checking daemon health, and confirming worker readiness using the rch doctor diagnostics workflow.

Yes, you can configure SSH keys and daemons for remote builds using this guided setup skill. It automates integration of SSH keys, validates daemon operation, and ensures all build machine prerequisites are met before routing compilation commands.

The best way to diagnose rch doctor and worker connection issues is running a guided diagnostics workflow that checks SSH access, daemon health, and worker readiness. This validates your workers.toml configuration and verifies hook installation across environments.

Yes, Rust nightly is a required prerequisite for the remote compilation helper. You must install Rust nightly alongside rsync and zstd on your machines to ensure the daemon operates correctly and workers function properly.