brainstorming
The Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it takes a one-line idea and drives it to an…
Verify the active host install, package, command ownership, enforcement, and harmless live-fire probe. Read-only.
$ npx -y skills add arbiterForge/codeArbiter --skill ca-doctor --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/ca-doctorContext preview
The summary Claude sees to decide when to auto-load this skill.
Verify the active host install, package, command ownership, enforcement, and harmless live-fire probe. Read-only.
name: ca-doctor description: Verify the active host install, package, command ownership, enforcement, and harmless live-fire probe. Read-only. argument-hint: (none)
Silent dormancy is the worst failure shape this plugin has: the gates look installed but never fire. This command proves the active host is healthy and reports every non-OK finding with an exact remediation.
1. Resolve the plugin root from this loaded skill path, then run its `hooks/doctor.py` with Python 3 and present the report verbatim. Do not try an empty plugin-root environment variable first. 2. In an arbiter-enabled repo, attempt `git add --all --dry-run` via the shell tool. `[H-03]` means hooks are firing; execution means **CRITICAL: gates dormant**.
1. Restart Codex so hooks register at session start. 2. Remove and re-add `ca-codex@codearbiter`, then approve the changed hook set in `/hooks`. 3. If dormancy was intended, `$ca-init` opts the repository in.
Read-only. MUST NOT create markers, stage files, grant trust, weaken a block, or retry the live-fire probe with different spelling. MUST surface a failed probe as CRITICAL, never as a footnote.
For an arbiter-enabled repository, the mechanical report treats the Git backstop as healthy only after exact managed-shim and live-enforcer validation, plus a harmless selected-Git `git hook run pre-push` probe with empty input. It never executes a foreign hook.
When you can't trust yourself with your code base, trust Arbiter.
Repo: arbiterForge/codeArbiter
The Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it takes a one-line idea and drives it to an…
The only path to a commit. Routed to when the user invokes /commit or otherwise instructs codeArbiter to persist staged changes. Nine gated phases —…
Optional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc…
The brownfield back-fill. Routed to by /create-context, and by startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker but source code…
The banned-primitive gate. Routed to when changed code hashes, signs, encrypts, derives keys, generates security-relevant randomness, configures TLS, or…
Investigate-then-decide root-cause analysis for a defect whose cause is unknown (distinct from /fix, which assumes a known bug). Five gated phases: capture,…