ce-setup

A lightweight health check and repo-local configuration helper for the Compound Engineering plugin. It verifies that an environment and repository are correctly set up, reports which optional tool capabilities are available, and cleans up or refreshes repo-local config files. Importantly, it does not bulk-install dependencies: missing tools are surfaced as optional capabilities so the user can install only the workflows they actually use. It is intended for verifying setup, troubleshooting missing optional tools, or onboarding a repository.

The workflow runs in three phases. In the diagnose phase it determines the installed plugin version when the platform exposes it, then runs a bundled check-health script (or an inline equivalent). The inline checks probe for optional tools with command -v (agent-browser, gh, jq, ast-grep, ffmpeg), resolve the repo root with git rev-parse --show-toplevel, look for an obsolete compound-engineering.local.md, check whether .compound-engineering/config.local.yaml exists and is gitignored, and compare the example config against the bundled references/config-template.yaml. Missing optional tools are explicitly not treated as setup failures.

Phase two only runs when a repo-local issue exists: an obsolete local Markdown config, a config.local.yaml that is not safely gitignored, or a missing/outdated example config. It can remove the obsolete file, refresh .compound-engineering/config.local.example.yaml from the template, optionally create a fresh config.local.yaml (everything starts commented out), and offer to add .compound-engineering/*.local.yaml to .gitignore. Every mutating step is gated behind a blocking question via the platform's question tool (AskUserQuestion in Claude Code, with documented fallbacks for Codex, Antigravity, and Pi), and the skill never silently auto-configures. A final summary lists fixes applied, fixes skipped, and any missing optional tools.