Skip to content
Development
Skill

/ca-doctor

Verify the active host install, package, command ownership, enforcement, and harmless live-fire probe. Read-only.

From plugin
codearbiter
14562 skills19 agents42 commands
Install
$ npx -y skills add arbiterForge/codeArbiter --skill ca-doctor --agent claude-code

How 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.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • 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.md
name: 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.

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.

Read more
Ships withcodearbiter

When you can't trust yourself with your code base, trust Arbiter.

Get the whole plugin

Other skills on codearbiter.