ca-arbiter
Exit maintainer dev mode — restore orchestration, remove the dev marker, log the exit.
npx skills add arbiterForge/codeArbiter --skill ca-arbiter --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# $ca-arbiter — restore orchestration The exit door for `$ca-dev`. No-op if dev mode is not active. ## Flow 1. **Log exit** — append to `<project-root>/.codearbiter/overrides.log` (append-only, `>>`): ``` [ISO-8601 timestamp] | BY: <email> | DEV: exit ``` 2. **Marker** — remove `<project-root>/.codearbiter/.markers/dev-active`. 3. **Resume** — re-present the startup state (stage, blocking `CONFIRM-NN`, in-flight tasks) and await a slash command. Orchestration, routing, and all gates are back in force. ## Hard gate MUST write the `DEV: exit` line to `overrides.log` and remove the `dev-active` marker before resuming orchestration — the exit is on the audit trail like the entry. MUST NOT rewrite or truncate `overrides.log` — the append-only rule has no dev exception, on entry or exit. If a prior session ended mid-dev, SessionStart has already appended the synthetic `BY: session-cleanup | DEV: exit` close line and cleared the marker (`session-start.py`, observability-001). In that case MUST NOT write a second `DEV: exit` for that orphaned entry — the close is already on the trail. Session-scoped clearing (#271): SessionStart's synthetic close is now conditional on the marker plausibly
- Flow
- Hard gate
What does the ca-arbiter skill do?
Exit maintainer dev mode — restore orchestration, remove the dev marker, log the exit.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-arbiter --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.