← ClaudeAtlas

cockpit-devlisted

Run this worktree's cockpit build against a throwaway sandbox, so it can't fight the installed daemon or touch real worktrees. TRIGGER on "run cockpit", "try it in the TUI", "does this render right". Not for pytest or `cockpit setup`.
khivi/cockpit · ★ 0 · Code & Development · score 75
Install: claude install-skill khivi/cockpit
# cockpit-dev Run `./dev.sh` from the repo root. It seeds `.cockpit-dev/` and execs this worktree's build against it. ```bash ./dev.sh # your real repos + a copy of your real PR cache, read-only ./dev.sh --empty # no repos — layout and keybinding work ./dev.sh -- nudge list # any other subcommand, same sandbox ``` `watch` is a Textual TUI and needs a terminal. If you're in a session without one, tell the user to run it themselves — suggest they type `! ./dev.sh` so the output lands in the conversation, or run it in their own terminal. ## What the sandbox does and does not cover `./dev.sh` isolates five things. Read `dev.sh`'s header comment for why each one is load-bearing; the short version is that missing any single one reaches real state: | Isolated | Covers | |---|---| | `COCKPIT_HOME` | `config.json`, PR cache | | `COCKPIT_RUNTIME_DIR` | `cockpit.pid`, close-request queue — a **separate** variable, because these are machine-local and deliberately do not follow `COCKPIT_HOME` | | `TMPDIR` | statusline/starship flat cells (they live in `$TMPDIR/cockpit-cache`, not under `COCKPIT_HOME`) | | `tool: none` | every cmux write — spawn, close, rename, set-color, workspace-group, `send` | | `--dry` | teardown, autoclose, `git branch -D`, tracker writes, spawn, nudge, the fast tick's cmux rename/recolour, and the row keys that reach outside (`n`/`f`/`h`/`a`, which refuse) | **Two things it does not cover, and you should say so rather than imply full