/ca-doctor
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.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/ca-doctor
Context 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.
SKILL.md
ca-doctor.SKILL.mdname: ca-doctor description: Verify the active host install, package, command ownership, enforcement, and harmless live-fire probe. Read-only. argument-hint: (none)
$ca-doctor — install health
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.
Flow
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**.
Remediation ladder
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.
When NOT to use
- Scaffold state only → `$ca-init --check`.
- Project progress, not install health → `$ca-status`.
Hard gate
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.
When you can't trust yourself with your code base, trust Arbiter.
Repo: arbiterForge/codeArbiter
Other skills on codearbiter.
- /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 approved, concrete spec with testable acceptance criteria. Four gated phases — frame, refine, write, approve. No
Open skill - /commit-gate
The only path to a commit. Routed to when the user invokes /commit or otherwise instructs codeArbiter to persist staged changes. Nine gated phases — permission, branch, classification, verification (test/lint/secrets), behavioral proof, diff review, selective stage, message,
Open skill - /context-check
Optional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
Open skill - /context-creation
The brownfield back-fill. Routed to by /create-context, and by startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker but source code exists. Six gated phases — pre-flight, scout dispatch, synthesis, gap interview, write, lock. Reads the existing codebase
Open skill - /crypto-compliance
The banned-primitive gate. Routed to when changed code hashes, signs, encrypts, derives keys, generates security-relevant randomness, configures TLS, or imports a crypto library. Rejects broken primitives, disabled TLS verification, and home-rolled crypto; the approved-primitive
Open skill - /debug
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, hypothesize, gather, decide, hand off. Investigation only, no code changes; exits to /fix, /adr, or a no-action close.
Open skill