/ca-status
Show the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only.
$ npx -y skills add arbiterForge/codeArbiter --skill ca-status --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-status
Context preview
The summary Claude sees to decide when to auto-load this skill.
Show the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only.
SKILL.md
ca-status.SKILL.mdname: ca-status
description: Show the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only.
argument-hint: (none)
$ca-status — state snapshot
A read-only summary of `.codearbiter/` state. No skill is routed to; no file is modified.
Flow
The orchestrator reads and presents:
1. **Stage** — the `stage:` maturity value from `<project-root>/.codearbiter/CONTEXT.md` frontmatter. 2. **Pipelines** — every slug in `<project-root>/.codearbiter/specs/` and `plans/`, with how far each got: spec awaiting approval, spec approved / no plan, plan in progress (`ACCEPTED` count vs. total from the plan's status column), or complete. An interrupted pipeline is resumable via `$ca-feature` — say so on its line. 3. **Open tasks** — the in-flight count from `<project-root>/.codearbiter/open-tasks.md` (top-level `- ` bullets excluding done `- [x]`; the same `_taskboardlib` count the SessionStart hook uses). 4. **Open questions** — the count of unresolved `[CONFIRM-NN]` placeholders in `<project-root>/.codearbiter/open-questions.md`. 5. **Overrides since last checkpoint** — entries in `<project-root>/.codearbiter/overrides.log` newer than the marker in `<project-root>/.codearbiter/last-checkpoint`. 6. **Current branch** — from git.
Output
## Project status — YYYY-MM-DD
Stage: N
Branch: <current branch>
Pipelines:
<slug> plan 3/7 ACCEPTED — resume with $ca-feature "<slug>"
<slug> spec approved, no plan
Open tasks: N
Open questions: N ([CONFIRM-NN] unresolved)
Overrides since last checkpoint: N
No specs and no plans → `Pipelines: none`.
If `[CONFIRM-NN]` placeholders are open, surface them — do not resolve them here.
When NOT to use
- A full cross-cutting review → `$ca-checkpoint`.
- A specific question → `$ca-btw`.
Hard gate
Read-only. MUST NOT modify any file. MUST NOT resolve a `[CONFIRM-NN]` it surfaces. No skill is routed to by this command.
Read more
name: ca-status description: Show the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only. argument-hint: (none)
$ca-status — state snapshot
A read-only summary of `.codearbiter/` state. No skill is routed to; no file is modified.
Flow
The orchestrator reads and presents:
1. **Stage** — the `stage:` maturity value from `<project-root>/.codearbiter/CONTEXT.md` frontmatter. 2. **Pipelines** — every slug in `<project-root>/.codearbiter/specs/` and `plans/`, with how far each got: spec awaiting approval, spec approved / no plan, plan in progress (`ACCEPTED` count vs. total from the plan's status column), or complete. An interrupted pipeline is resumable via `$ca-feature` — say so on its line. 3. **Open tasks** — the in-flight count from `<project-root>/.codearbiter/open-tasks.md` (top-level `- ` bullets excluding done `- [x]`; the same `_taskboardlib` count the SessionStart hook uses). 4. **Open questions** — the count of unresolved `[CONFIRM-NN]` placeholders in `<project-root>/.codearbiter/open-questions.md`. 5. **Overrides since last checkpoint** — entries in `<project-root>/.codearbiter/overrides.log` newer than the marker in `<project-root>/.codearbiter/last-checkpoint`. 6. **Current branch** — from git.
Output
## Project status — YYYY-MM-DD Stage: N Branch: <current branch> Pipelines: <slug> plan 3/7 ACCEPTED — resume with $ca-feature "<slug>" <slug> spec approved, no plan Open tasks: N Open questions: N ([CONFIRM-NN] unresolved) Overrides since last checkpoint: N
No specs and no plans → `Pipelines: none`.
If `[CONFIRM-NN]` placeholders are open, surface them — do not resolve them here.
When NOT to use
- A full cross-cutting review → `$ca-checkpoint`.
- A specific question → `$ca-btw`.
Hard gate
Read-only. MUST NOT modify any file. MUST NOT resolve a `[CONFIRM-NN]` it surfaces. No skill is routed to by this command.
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

