GitHub collection
arbiterforge/codearbiter
Imported from GitHub — is this yours?
149 skills imported from this repository.
- Stars
- 152
- Forks
- 9
- License
- AGPL-3.0
Skills (149)
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. Five gated phases — frame, shape, refine, write, review-and-appro
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, comm
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.
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 t
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
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.
decision-lifecycle
Author and track Architecture Decision Records. Routed to when the user invokes /adr to record a new decision or /adr-status to list ADR health. Authors numbered, dated, user-attributed ADRs under .codearbiter/decisions/, maintains supersede chains, and reports status read-only.
decision-variance
Reconcile the project's architectural artifacts against the scaffold and prior decisions, then present each variance as a SMARTS analysis for the user to decide. Routed to when the user asks to arbitrate, reconcile, or consolidate architectural context, requests a variance report
decompose
The greenfield decomposition interview. Routed to at startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker and no source code exists, or when the user invokes /decompose. A senior-architect persona drives a six-layer interview, persists every layer to disk
dispatching-parallel-agents
The parallel fan-out primitive. Routed to by any skill or command that splits work across independent units and dispatches an agent per unit — subagent-driven-development, /sprint, parallel /review. It owns the dispatch/collect/funnel discipline: bound concurrency, isolate units,
executing-plans
The checkpoint coordinator for /feature. Routed to by /feature once a writing-plans plan exists. Groups tasks into batches, delegates each batch to subagent-driven-development (fresh author agent per task, full review chain, fresh verification), then stops for a human checkpoint
finishing-a-development-branch
The terminal step of /feature and /sprint. Routed to once commit-gate has cleared, to decide the branch's fate — merge via PR, open a PR, or discard. Direct merge to the default branch is forbidden; every change lands through a PR. Under /sprint the skill auto-selects "open PR" a
post-merge-cleanup
Finish an already-merged branch. Proves the branch is contained in the fetched default, classifies leftover artifacts as unique / redundant / superseded, returns to a clean --ff-only default checkout, and deletes the merged local branch — every discard confirmed per item. Routed
refactor
The behavior-preserving restructure gate. Routed to by /refactor for a rename, extract, inline, move, dedup, or internal-implementation swap. Six gated phases prove behavioral parity through unmodified pre-existing tests; any diff that classifies as `feat` is not a refactor and i
release
The single permitted path to a version tag, for any target declared in the project's .codearbiter/release-targets.md. Routed to when the user invokes /release on a non-default branch with a green suite. Takes the declared target as its one argument, derives the SemVer bump from C
secret-handling
The secret-source gate. Routed to when changed code reads, writes, or passes a secret — API key, token, password, connection string, signing key, certificate, or any value that grants access. Validates that every secret comes from the approved store and never lands in source, log
security-architecture
Optional, opt-in STRIDE threat pass for a sensitive feature — invoked deliberately via /threat-model, never forced on ordinary changes. Walks the change's attack surface and security boundaries (governed by {{PROJECT_DIR}}/.codearbiter/security-controls.md), surfaces threats and
tdd
The test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation code is written. Six gated phases — obligation scan, red, green, obligation verify, coverage, lint. No feature code exists before Phase 1 clears; nothing reaches
tribunal
The deep, rarely-convened whole-codebase audit lane. Routed to when the user invokes {{CMD:tribunal}}. Seven gated phases — cost/model, map, roster dispatch, triage, report, approval+filing, telemetry. Costs on the order of millions of tokens; proceeds only after the user acknowl
using-git-worktrees
OPTIONAL per-task isolation for autonomous parallel work. Routed to only on explicit opt-in by subagent-driven-development or dispatching-parallel-agents, so parallel units mutate files without colliding. Stands up one worktree per unit, works it in isolation, then integrates eac
writing-plans
The spec-to-plan bridge. Routed to by /feature once the brainstormed spec is approved, and by /sprint before execution. Decomposes the spec into 2–5 minute tasks, each carrying its exact file path(s) and a concrete verification step that maps to a tdd obligation. Writes the plan
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. Five gated phases — frame, shape, refine, write, review-and-appro
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, comm
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.
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 t
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
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.
decision-lifecycle
Author and track Architecture Decision Records. Routed to when the user invokes /adr to record a new decision or /adr-status to list ADR health. Authors numbered, dated, user-attributed ADRs under .codearbiter/decisions/, maintains supersede chains, and reports status read-only.
decision-variance
Reconcile the project's architectural artifacts against the scaffold and prior decisions, then present each variance as a SMARTS analysis for the user to decide. Routed to when the user asks to arbitrate, reconcile, or consolidate architectural context, requests a variance report
decompose
The greenfield decomposition interview. Routed to at startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker and no source code exists, or when the user invokes /decompose. A senior-architect persona drives a six-layer interview, persists every layer to disk
dispatching-parallel-agents
The parallel fan-out primitive. Routed to by any skill or command that splits work across independent units and dispatches an agent per unit — subagent-driven-development, /sprint, parallel /review. It owns the dispatch/collect/funnel discipline: bound concurrency, isolate units,
executing-plans
The checkpoint coordinator for /feature. Routed to by /feature once a writing-plans plan exists. Groups tasks into batches, delegates each batch to subagent-driven-development (fresh author agent per task, full review chain, fresh verification), then stops for a human checkpoint
finishing-a-development-branch
The terminal step of /feature and /sprint. Routed to once commit-gate has cleared, to decide the branch's fate — merge via PR, open a PR, or discard. Direct merge to the default branch is forbidden; every change lands through a PR. Under /sprint the skill auto-selects "open PR" a
post-merge-cleanup
Finish an already-merged branch. Proves the branch is contained in the fetched default, classifies leftover artifacts as unique / redundant / superseded, returns to a clean --ff-only default checkout, and deletes the merged local branch — every discard confirmed per item. Routed
refactor
The behavior-preserving restructure gate. Routed to by /refactor for a rename, extract, inline, move, dedup, or internal-implementation swap. Six gated phases prove behavioral parity through unmodified pre-existing tests; any diff that classifies as `feat` is not a refactor and i
release
The single permitted path to a version tag, for any target declared in the project's .codearbiter/release-targets.md. Routed to when the user invokes /release on a non-default branch with a green suite. Takes the declared target as its one argument, derives the SemVer bump from C
secret-handling
The secret-source gate. Routed to when changed code reads, writes, or passes a secret — API key, token, password, connection string, signing key, certificate, or any value that grants access. Validates that every secret comes from the approved store and never lands in source, log
security-architecture
Optional, opt-in STRIDE threat pass for a sensitive feature — invoked deliberately via /threat-model, never forced on ordinary changes. Walks the change's attack surface and security boundaries (governed by <project-root>/.codearbiter/security-controls.md), surfaces threats and u
tdd
The test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation code is written. Six gated phases — obligation scan, red, green, obligation verify, coverage, lint. No feature code exists before Phase 1 clears; nothing reaches
tribunal
The deep, rarely-convened whole-codebase audit lane. Routed to when the user invokes $ca-tribunal. Seven gated phases — cost/model, map, roster dispatch, triage, report, approval+filing, telemetry. Costs on the order of millions of tokens; proceeds only after the user acknowledge
using-git-worktrees
OPTIONAL per-task isolation for autonomous parallel work. Routed to only on explicit opt-in by subagent-driven-development or dispatching-parallel-agents, so parallel units mutate files without colliding. Stands up one worktree per unit, works it in isolation, then integrates eac
writing-plans
The spec-to-plan bridge. Routed to by /feature once the brainstormed spec is approved, and by /sprint before execution. Decomposes the spec into 2–5 minute tasks, each carrying its exact file path(s) and a concrete verification step that maps to a tdd obligation. Writes the plan
ca-add-dep
Vet a new or changed third-party dependency for license, provenance, and supply-chain risk before any install runs.
ca-adr-status
Report the health of Architecture Decision Records — aged, unchallenged, supersession candidates, unresolved CONFIRM-NN. Read-only.
ca-checkpoint
Periodic multi-reviewer sweep of the whole codebase — surfaces a triaged checkpoint report.
ca-cleanup
Finish an already-merged branch — classify the leftover artifacts, return to a fast-forwarded default checkout, and delete the merged local branch. Every discard confirmed per item; containment proven, never assumed.
ca-conflict
Stop everything and surface a rule conflict — persona vs. docs vs. code. Present both sides and the conflict-hierarchy level; the user resolves. No silent reconciliation.
ca-context-check
Optional manual drift audit — report stale provenance-tracked docs, then per stale doc offer re-scout, re-baseline, or defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
ca-create-context
Brownfield back-fill — scout an existing codebase and populate .codearbiter/, then lock it initialized.
ca-decompose
Greenfield decomposition interview — a layered interview that populates .codearbiter/ and locks it initialized.
ca-feature
Start a feature: brainstorm a spec, get it approved, then drive it test-first through the pipeline. The one entry to implementation.
ca-override
Sanctioned, logged bypass of a gate or hard rule — one audit line, then proceed.
ca-reconcile
SMARTS arbitration — reconcile architectural artifacts against the scaffold and prior decisions; every variance resolved by an explicit, user-attributed choice.
ca-refactor
Restructure code with behavioral parity proven through unmodified pre-existing tests, then refactor. No behavior change.
ca-release
Cut a release the only sanctioned way — SemVer bump from the commit log, a CHANGELOG section, an annotated tag. Takes the declared target's name as its only argument, or --dry-run to preview one with no write. The only path to a version tag.
ca-standup
Daily repo hygiene — review the day's repo state, then perform the cleanups under per-action confirmation. Fast-forward only, never destructive without a yes.
ca-threat-model
Opt-in lightweight STRIDE pass for a sensitive feature before implementation. Not a routine gate — invoke it when a change warrants security thought.
ca-tribunal
Deep, rarely-convened whole-codebase audit — eleven specialist lenses, a resumable on-disk audit log, findings filed as GitHub issues on approval. Expensive; estimates cost and STOPs before running. Never a required gate.
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. Five gated phases — frame, shape, refine, write, review-and-appro
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, comm
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.
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 t
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
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.
decision-lifecycle
Author and track Architecture Decision Records. Routed to when the user invokes /adr to record a new decision or /adr-status to list ADR health. Authors numbered, dated, user-attributed ADRs under .codearbiter/decisions/, maintains supersede chains, and reports status read-only.
decision-variance
Reconcile the project's architectural artifacts against the scaffold and prior decisions, then present each variance as a SMARTS analysis for the user to decide. Routed to when the user asks to arbitrate, reconcile, or consolidate architectural context, requests a variance report
decompose
The greenfield decomposition interview. Routed to at startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker and no source code exists, or when the user invokes /decompose. A senior-architect persona drives a six-layer interview, persists every layer to disk
dispatching-parallel-agents
The parallel fan-out primitive. Routed to by any skill or command that splits work across independent units and dispatches an agent per unit — subagent-driven-development, /sprint, parallel /review. It owns the dispatch/collect/funnel discipline: bound concurrency, isolate units,
executing-plans
The checkpoint coordinator for /feature. Routed to by /feature once a writing-plans plan exists. Groups tasks into batches, delegates each batch to subagent-driven-development (fresh author agent per task, full review chain, fresh verification), then stops for a human checkpoint
finishing-a-development-branch
The terminal step of /feature and /sprint. Routed to once commit-gate has cleared, to decide the branch's fate — merge via PR, open a PR, or discard. Direct merge to the default branch is forbidden; every change lands through a PR. Under /sprint the skill auto-selects "open PR" a
post-merge-cleanup
Finish an already-merged branch. Proves the branch is contained in the fetched default, classifies leftover artifacts as unique / redundant / superseded, returns to a clean --ff-only default checkout, and deletes the merged local branch — every discard confirmed per item. Routed
refactor
The behavior-preserving restructure gate. Routed to by /refactor for a rename, extract, inline, move, dedup, or internal-implementation swap. Six gated phases prove behavioral parity through unmodified pre-existing tests; any diff that classifies as `feat` is not a refactor and i
release
The single permitted path to a version tag, for any target declared in the project's .codearbiter/release-targets.md. Routed to when the user invokes /release on a non-default branch with a green suite. Takes the declared target as its one argument, derives the SemVer bump from C
secret-handling
The secret-source gate. Routed to when changed code reads, writes, or passes a secret — API key, token, password, connection string, signing key, certificate, or any value that grants access. Validates that every secret comes from the approved store and never lands in source, log
security-architecture
Optional, opt-in STRIDE threat pass for a sensitive feature — invoked deliberately via /threat-model, never forced on ordinary changes. Walks the change's attack surface and security boundaries (governed by <project-root>/.codearbiter/security-controls.md), surfaces threats and u
tdd
The test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation code is written. Six gated phases — obligation scan, red, green, obligation verify, coverage, lint. No feature code exists before Phase 1 clears; nothing reaches
tribunal
The deep, rarely-convened whole-codebase audit lane. Routed to when the user invokes /ca-tribunal. Seven gated phases — cost/model, map, roster dispatch, triage, report, approval+filing, telemetry. Costs on the order of millions of tokens; proceeds only after the user acknowledge
using-git-worktrees
OPTIONAL per-task isolation for autonomous parallel work. Routed to only on explicit opt-in by subagent-driven-development or dispatching-parallel-agents, so parallel units mutate files without colliding. Stands up one worktree per unit, works it in isolation, then integrates eac
writing-plans
The spec-to-plan bridge. Routed to by /feature once the brainstormed spec is approved, and by /sprint before execution. Decomposes the spec into 2–5 minute tasks, each carrying its exact file path(s) and a concrete verification step that maps to a tdd obligation. Writes the plan
ca-add-dep
Vet a new or changed third-party dependency for license, provenance, and supply-chain risk before any install runs.
ca-adr-status
Report the health of Architecture Decision Records — aged, unchallenged, supersession candidates, unresolved CONFIRM-NN. Read-only.
ca-checkpoint
Periodic multi-reviewer sweep of the whole codebase — surfaces a triaged checkpoint report.
ca-cleanup
Finish an already-merged branch — classify the leftover artifacts, return to a fast-forwarded default checkout, and delete the merged local branch. Every discard confirmed per item; containment proven, never assumed.
ca-conflict
Stop everything and surface a rule conflict — persona vs. docs vs. code. Present both sides and the conflict-hierarchy level; the user resolves. No silent reconciliation.
ca-context-check
Optional manual drift audit — report stale provenance-tracked docs, then per stale doc offer re-scout, re-baseline, or defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
ca-create-context
Brownfield back-fill — scout an existing codebase and populate .codearbiter/, then lock it initialized.
ca-decompose
Greenfield decomposition interview — a layered interview that populates .codearbiter/ and locks it initialized.
ca-feature
Start a feature: brainstorm a spec, get it approved, then drive it test-first through the pipeline. The one entry to implementation.
ca-override
Sanctioned, logged bypass of a gate or hard rule — one audit line, then proceed.
ca-reconcile
SMARTS arbitration — reconcile architectural artifacts against the scaffold and prior decisions; every variance resolved by an explicit, user-attributed choice.
ca-refactor
Restructure code with behavioral parity proven through unmodified pre-existing tests, then refactor. No behavior change.
ca-release
Cut a release the only sanctioned way — SemVer bump from the commit log, a CHANGELOG section, an annotated tag. Takes the declared target's name as its only argument, or --dry-run to preview one with no write. The only path to a version tag.
ca-standup
Daily repo hygiene — review the day's repo state, then perform the cleanups under per-action confirmation. Fast-forward only, never destructive without a yes.
ca-threat-model
Opt-in lightweight STRIDE pass for a sensitive feature before implementation. Not a routine gate — invoke it when a change warrants security thought.
ca-tribunal
Deep, rarely-convened whole-codebase audit — eleven specialist lenses, a resumable on-disk audit log, findings filed as GitHub issues on approval. Expensive; estimates cost and STOPs before running. Never a required gate.
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. Five gated phases — frame, shape, refine, write, review-and-appro
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, comm
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.
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 t
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
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.
decision-lifecycle
Author and track Architecture Decision Records. Routed to when the user invokes /adr to record a new decision or /adr-status to list ADR health. Authors numbered, dated, user-attributed ADRs under .codearbiter/decisions/, maintains supersede chains, and reports status read-only.
decision-variance
Reconcile the project's architectural artifacts against the scaffold and prior decisions, then present each variance as a SMARTS analysis for the user to decide. Routed to when the user asks to arbitrate, reconcile, or consolidate architectural context, requests a variance report
decompose
The greenfield decomposition interview. Routed to at startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker and no source code exists, or when the user invokes /decompose. A senior-architect persona drives a six-layer interview, persists every layer to disk
dispatching-parallel-agents
The parallel fan-out primitive. Routed to by any skill or command that splits work across independent units and dispatches an agent per unit — subagent-driven-development, /sprint, parallel /review. It owns the dispatch/collect/funnel discipline: bound concurrency, isolate units,
executing-plans
The checkpoint coordinator for /feature. Routed to by /feature once a writing-plans plan exists. Groups tasks into batches, delegates each batch to subagent-driven-development (fresh author agent per task, full review chain, fresh verification), then stops for a human checkpoint
finishing-a-development-branch
The terminal step of /feature and /sprint. Routed to once commit-gate has cleared, to decide the branch's fate — merge via PR, open a PR, or discard. Direct merge to the default branch is forbidden; every change lands through a PR. Under /sprint the skill auto-selects "open PR" a
post-merge-cleanup
Finish an already-merged branch. Proves the branch is contained in the fetched default, classifies leftover artifacts as unique / redundant / superseded, returns to a clean --ff-only default checkout, and deletes the merged local branch — every discard confirmed per item. Routed
refactor
The behavior-preserving restructure gate. Routed to by /refactor for a rename, extract, inline, move, dedup, or internal-implementation swap. Six gated phases prove behavioral parity through unmodified pre-existing tests; any diff that classifies as `feat` is not a refactor and i
release
The single permitted path to a version tag, for any target declared in the project's .codearbiter/release-targets.md. Routed to when the user invokes /release on a non-default branch with a green suite. Takes the declared target as its one argument, derives the SemVer bump from C
secret-handling
The secret-source gate. Routed to when changed code reads, writes, or passes a secret — API key, token, password, connection string, signing key, certificate, or any value that grants access. Validates that every secret comes from the approved store and never lands in source, log
security-architecture
Optional, opt-in STRIDE threat pass for a sensitive feature — invoked deliberately via /threat-model, never forced on ordinary changes. Walks the change's attack surface and security boundaries (governed by ${CLAUDE_PROJECT_DIR}/.codearbiter/security-controls.md), surfaces threat
tdd
The test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation code is written. Six gated phases — obligation scan, red, green, obligation verify, coverage, lint. No feature code exists before Phase 1 clears; nothing reaches
tribunal
The deep, rarely-convened whole-codebase audit lane. Routed to when the user invokes /ca:tribunal. Seven gated phases — cost/model, map, roster dispatch, triage, report, approval+filing, telemetry. Costs on the order of millions of tokens; proceeds only after the user acknowledge
using-git-worktrees
OPTIONAL per-task isolation for autonomous parallel work. Routed to only on explicit opt-in by subagent-driven-development or dispatching-parallel-agents, so parallel units mutate files without colliding. Stands up one worktree per unit, works it in isolation, then integrates eac
writing-plans
The spec-to-plan bridge. Routed to by /feature once the brainstormed spec is approved, and by /sprint before execution. Decomposes the spec into 2–5 minute tasks, each carrying its exact file path(s) and a concrete verification step that maps to a tdd obligation. Writes the plan
sandbox-claude-inside
Run Claude Code INSIDE a ca-sandbox box (`--with-claude`). Routed to when the user wants an agent loop running against an isolated, ephemeral sandbox rather than the host. Authenticates via an env-injected CLAUDE_CODE_OAUTH_TOKEN with no host bind of ~/.claude; the image pins the
sandbox-lifecycle
The lifecycle gate for a local Codespace-equivalent sandbox. Routed to when the user invokes /ca-sandbox:sandbox to pull an untrusted repo into an ephemeral, host-FS-isolated Docker container, or any of the interaction commands (/ca-sandbox:sandbox-shell, /ca-sandbox:sandbox-exec
Agents (75)
architecture-drift-reviewer
Read-only checkpoint reviewer. Surfaces drift between the codebase and accepted ADRs in .codearbiter/decisions/. Informational — never blocks.
auth-crypto-reviewer
Reviews authentication, cryptography, key handling, and secrets against {{PROJECT_DIR}}/.codearbiter/security-controls.md. Hard blocks on banned primitives, exposed secrets, disabled TLS verification, and shell injection. Read-only checkpoint reviewer.
backend-author
Use when writing or modifying backend/server-side code. Owns the TDD workflow, input validation, framework conventions, and ORM usage. MUST write failing tests before implementation code. Reads tech stack from {{PROJECT_DIR}}/.codearbiter/tech-stack.md.
checkpoint-aggregator
Composes the finding-triage report and decision-challenger output into a dated checkpoint document under .codearbiter/checkpoints/YYYY-MM-DD.md. Aggregator, not a blocker.
coverage-auditor
Dispatched by the tdd skill (Phase 4) to audit test coverage against TDD obligations. Identifies untested source files, coverage below the maturity threshold, and logical test gaps.
decision-challenger
Adversarial red-team reviewer of ADRs. Builds the strongest case against each decision, names load-bearing assumptions, assigns confidence 1–5, and surfaces evidence that would prove a decision wrong. Read-only. Dispatched optionally by decision-variance. Reads ADRs from .codearb
dependency-reviewer
Dispatched when package.json, lock files, or container base images change. Verifies license, provenance, maintenance signal, and supply-chain posture against .codearbiter/security-controls.md and .codearbiter/tech-stack.md before merge.
design-quality-reviewer
Reviews generated, user-facing visual or formatted output (UI, reports, slides, charts, diagrams, CLI output) against the anti-slop-design reference. Read-only; surfaces design-slop findings. Dispatched by frontend-author on UI changes. Tier 2 document producers (/pr, release) ap
finding-triage
Post-processes all checkpoint reviewer reports — consolidates findings, classifies each by severity and whether it blocks the current change. Sequential. Produces a unified triage report for the checkpoint-aggregator. Reads project state from .codearbiter/.
frontend-author
Use when writing or modifying frontend/UI code. Owns the TDD workflow, component conventions, state management, and UI security. MUST write failing tests before implementation code. Reads tech stack from {{PROJECT_DIR}}/.codearbiter/tech-stack.md.
grader
INTERNAL SMARTS analyst dispatched by the decision-variance skill. Produces a SMARTS analysis and recommendation for one (artifact-position, scaffold-evidence) pair. Never decides — the user decides. Never dispatch directly.
infra-author
Use when writing or modifying IaC, containers, CI/CD manifests, or deployment configuration. Reads tech stack and security boundaries from {{PROJECT_DIR}}/.codearbiter/.
map-deps
Dispatched by the tribunal deep-audit lane's Phase 1, on a large/sprawling repo, to offload dependency/integration-surface mapping out of the orchestrator's retained context. Read-only extractor, not a judge — reports facts, files no findings.
map-structure
Dispatched by the tribunal deep-audit lane's Phase 1, on a large/sprawling repo, to offload structural mapping out of the orchestrator's retained context. Read-only extractor, not a judge — reports facts, files no findings.
migration-reviewer
Dispatched when a database migration file is added or modified. Reviews migrations for safety, data-classification tagging, and immutability against .codearbiter/security-controls.md.
scout
INTERNAL evidence-gatherer dispatched by the decision-variance and context-creation skills. Scans an assigned code scope and reports evidence of architectural decisions — file paths and line numbers only. Never dispatch directly.
security-reviewer
Dispatch PROACTIVELY when a change touches authentication, authorization, cryptography, secrets, deployment manifests, network policies, or CI workflows. Reviews diffs against {{PROJECT_DIR}}/.codearbiter/security-controls.md. Read-only; produces findings.
tribunal-lens-reviewer
Dispatched by the tribunal deep-audit lane, once per active lens, with a lens assignment. Generic read-only lens executor — reads the assigned lens mandate under skills/tribunal/references/lenses/ and writes one file per finding. Never dispatch directly.
architecture-drift-reviewer
Read-only checkpoint reviewer. Surfaces drift between the codebase and accepted ADRs in .codearbiter/decisions/. Informational — never blocks.
auth-crypto-reviewer
Reviews authentication, cryptography, key handling, and secrets against ${CLAUDE_PROJECT_DIR}/.codearbiter/security-controls.md. Hard blocks on banned primitives, exposed secrets, disabled TLS verification, and shell injection. Read-only checkpoint reviewer.
backend-author
Use when writing or modifying backend/server-side code. Owns the TDD workflow, input validation, framework conventions, and ORM usage. MUST write failing tests before implementation code. Reads tech stack from ${CLAUDE_PROJECT_DIR}/.codearbiter/tech-stack.md.
checkpoint-aggregator
Composes the finding-triage report and decision-challenger output into a dated checkpoint document under .codearbiter/checkpoints/YYYY-MM-DD.md. Aggregator, not a blocker.
coverage-auditor
Dispatched by the tdd skill (Phase 4) to audit test coverage against TDD obligations. Identifies untested source files, coverage below the maturity threshold, and logical test gaps.
decision-challenger
Adversarial red-team reviewer of ADRs. Builds the strongest case against each decision, names load-bearing assumptions, assigns confidence 1–5, and surfaces evidence that would prove a decision wrong. Read-only. Dispatched optionally by decision-variance. Reads ADRs from .codearb
dependency-reviewer
Dispatched when package.json, lock files, or container base images change. Verifies license, provenance, maintenance signal, and supply-chain posture against .codearbiter/security-controls.md and .codearbiter/tech-stack.md before merge.
design-quality-reviewer
Reviews generated, user-facing visual or formatted output (UI, reports, slides, charts, diagrams, CLI output) against the anti-slop-design reference. Read-only; surfaces design-slop findings. Dispatched by frontend-author on UI changes. Tier 2 document producers (/pr, release) ap
finding-triage
Post-processes all checkpoint reviewer reports — consolidates findings, classifies each by severity and whether it blocks the current change. Sequential. Produces a unified triage report for the checkpoint-aggregator. Reads project state from .codearbiter/.
frontend-author
Use when writing or modifying frontend/UI code. Owns the TDD workflow, component conventions, state management, and UI security. MUST write failing tests before implementation code. Reads tech stack from ${CLAUDE_PROJECT_DIR}/.codearbiter/tech-stack.md.
grader
INTERNAL SMARTS analyst dispatched by the decision-variance skill. Produces a SMARTS analysis and recommendation for one (artifact-position, scaffold-evidence) pair. Never decides — the user decides. Never dispatch directly.
infra-author
Use when writing or modifying IaC, containers, CI/CD manifests, or deployment configuration. Reads tech stack and security boundaries from ${CLAUDE_PROJECT_DIR}/.codearbiter/.
map-deps
Dispatched by the tribunal deep-audit lane's Phase 1, on a large/sprawling repo, to offload dependency/integration-surface mapping out of the orchestrator's retained context. Read-only extractor, not a judge — reports facts, files no findings.
map-structure
Dispatched by the tribunal deep-audit lane's Phase 1, on a large/sprawling repo, to offload structural mapping out of the orchestrator's retained context. Read-only extractor, not a judge — reports facts, files no findings.
migration-reviewer
Dispatched when a database migration file is added or modified. Reviews migrations for safety, data-classification tagging, and immutability against .codearbiter/security-controls.md.
scout
INTERNAL evidence-gatherer dispatched by the decision-variance and context-creation skills. Scans an assigned code scope and reports evidence of architectural decisions — file paths and line numbers only. Never dispatch directly.
security-reviewer
Dispatch PROACTIVELY when a change touches authentication, authorization, cryptography, secrets, deployment manifests, network policies, or CI workflows. Reviews diffs against ${CLAUDE_PROJECT_DIR}/.codearbiter/security-controls.md. Read-only; produces findings.
tribunal-lens-reviewer
Dispatched by the tribunal deep-audit lane, once per active lens, with a lens assignment. Generic read-only lens executor — reads the assigned lens mandate under skills/tribunal/references/lenses/ and writes one file per finding. Never dispatch directly.
architecture-drift-reviewer
Read-only checkpoint reviewer. Surfaces drift between the codebase and accepted ADRs in .codearbiter/decisions/. Informational — never blocks.
auth-crypto-reviewer
Reviews authentication, cryptography, key handling, and secrets against <project-root>/.codearbiter/security-controls.md. Hard blocks on banned primitives, exposed secrets, disabled TLS verification, and shell injection. Read-only checkpoint reviewer.
backend-author
Use when writing or modifying backend/server-side code. Owns the TDD workflow, input validation, framework conventions, and ORM usage. MUST write failing tests before implementation code. Reads tech stack from <project-root>/.codearbiter/tech-stack.md.
checkpoint-aggregator
Composes the finding-triage report and decision-challenger output into a dated checkpoint document under .codearbiter/checkpoints/YYYY-MM-DD.md. Aggregator, not a blocker.
coverage-auditor
Dispatched by the tdd skill (Phase 4) to audit test coverage against TDD obligations. Identifies untested source files, coverage below the maturity threshold, and logical test gaps.
decision-challenger
Adversarial red-team reviewer of ADRs. Builds the strongest case against each decision, names load-bearing assumptions, assigns confidence 1–5, and surfaces evidence that would prove a decision wrong. Read-only. Dispatched optionally by decision-variance. Reads ADRs from .codearb
dependency-reviewer
Dispatched when package.json, lock files, or container base images change. Verifies license, provenance, maintenance signal, and supply-chain posture against .codearbiter/security-controls.md and .codearbiter/tech-stack.md before merge.
design-quality-reviewer
Reviews generated, user-facing visual or formatted output (UI, reports, slides, charts, diagrams, CLI output) against the anti-slop-design reference. Read-only; surfaces design-slop findings. Dispatched by frontend-author on UI changes. Tier 2 document producers (/pr, release) ap
finding-triage
Post-processes all checkpoint reviewer reports — consolidates findings, classifies each by severity and whether it blocks the current change. Sequential. Produces a unified triage report for the checkpoint-aggregator. Reads project state from .codearbiter/.
frontend-author
Use when writing or modifying frontend/UI code. Owns the TDD workflow, component conventions, state management, and UI security. MUST write failing tests before implementation code. Reads tech stack from <project-root>/.codearbiter/tech-stack.md.
grader
INTERNAL SMARTS analyst dispatched by the decision-variance skill. Produces a SMARTS analysis and recommendation for one (artifact-position, scaffold-evidence) pair. Never decides — the user decides. Never dispatch directly.
infra-author
Use when writing or modifying IaC, containers, CI/CD manifests, or deployment configuration. Reads tech stack and security boundaries from <project-root>/.codearbiter/.
map-deps
Dispatched by the tribunal deep-audit lane's Phase 1, on a large/sprawling repo, to offload dependency/integration-surface mapping out of the orchestrator's retained context. Read-only extractor, not a judge — reports facts, files no findings.
map-structure
Dispatched by the tribunal deep-audit lane's Phase 1, on a large/sprawling repo, to offload structural mapping out of the orchestrator's retained context. Read-only extractor, not a judge — reports facts, files no findings.
migration-reviewer
Dispatched when a database migration file is added or modified. Reviews migrations for safety, data-classification tagging, and immutability against .codearbiter/security-controls.md.
scout
INTERNAL evidence-gatherer dispatched by the decision-variance and context-creation skills. Scans an assigned code scope and reports evidence of architectural decisions — file paths and line numbers only. Never dispatch directly.
security-reviewer
Dispatch PROACTIVELY when a change touches authentication, authorization, cryptography, secrets, deployment manifests, network policies, or CI workflows. Reviews diffs against <project-root>/.codearbiter/security-controls.md. Read-only; produces findings.
tribunal-lens-reviewer
Dispatched by the tribunal deep-audit lane, once per active lens, with a lens assignment. Generic read-only lens executor — reads the assigned lens mandate under skills/tribunal/references/lenses/ and writes one file per finding. Never dispatch directly.
architecture-drift-reviewer
Imported from arbiterforge/codearbiter/site/src/curated/agents/architecture-drift-reviewer.md.
auth-crypto-reviewer
Imported from arbiterforge/codearbiter/site/src/curated/agents/auth-crypto-reviewer.md.
backend-author
Imported from arbiterforge/codearbiter/site/src/curated/agents/backend-author.md.
checkpoint-aggregator
Imported from arbiterforge/codearbiter/site/src/curated/agents/checkpoint-aggregator.md.
coverage-auditor
Imported from arbiterforge/codearbiter/site/src/curated/agents/coverage-auditor.md.
decision-challenger
Imported from arbiterforge/codearbiter/site/src/curated/agents/decision-challenger.md.
dependency-reviewer
Imported from arbiterforge/codearbiter/site/src/curated/agents/dependency-reviewer.md.
design-quality-reviewer
Imported from arbiterforge/codearbiter/site/src/curated/agents/design-quality-reviewer.md.
finding-triage
Imported from arbiterforge/codearbiter/site/src/curated/agents/finding-triage.md.
frontend-author
Imported from arbiterforge/codearbiter/site/src/curated/agents/frontend-author.md.
infra-author
Imported from arbiterforge/codearbiter/site/src/curated/agents/infra-author.md.
map-structure
Imported from arbiterforge/codearbiter/site/src/curated/agents/map-structure.md.
migration-reviewer
Imported from arbiterforge/codearbiter/site/src/curated/agents/migration-reviewer.md.
security-reviewer
Imported from arbiterforge/codearbiter/site/src/curated/agents/security-reviewer.md.
tribunal-lens-reviewer
Imported from arbiterforge/codearbiter/site/src/curated/agents/tribunal-lens-reviewer.md.
Commands (108)
-
source
/add-dep— Reviews a new or changed third-party dependency before adoption. The read-only -
source
/add-dep— Vet a new or changed third-party dependency for license, provenance, and supply-chain risk before any install runs. -
source
/add-dep— Vet a new or changed third-party dependency for license, provenance, and supply-chain risk before any install runs. -
source
/adr— Records an architectural decision as a numbered, dated ADR under `.codearbiter/decisions/`. -
source
/adr— {{SKILL_ENTRY:decision-lifecycle}} -
source
/adr— Record user-decided ADRs or inspect their health read-only. Preserve attribution and acceptance evidence. -
source
/adr-status— A read-only health scan of every recorded ADR under `.codearbiter/decisions/`. For each one it -
source
/adr-status— Inspect ADR health read-only; optionally select one ADR with --adr N. -
source
/adr-status— Inspect ADR health read-only; optionally select one ADR with --adr N. -
source
/another— Another command, description only, no argument hint. -
source
/audit— Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only. -
source
/audit— Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only. -
source
/audit— Assembles everything codeArbiter logs — `overrides.log`, `triage.log`, `decisions/`, -
source
/checkpoint— Periodic multi-reviewer sweep of the whole codebase — surfaces a triaged checkpoint report. -
source
/checkpoint— Periodic multi-reviewer sweep of the whole codebase — surfaces a triaged checkpoint report. -
source
/checkpoint— A periodic whole-repository review. The caller supplies the reviewer unit list to -
source
/chore— Sanctioned lane for non-behavioral work — docs-only edits, dependency bumps, reverts. Type-scaled gates; no TDD demanded of prose. -
source
/chore— Sanctioned lane for non-behavioral work — docs-only edits, dependency bumps, reverts. Type-scaled gates; no TDD demanded of prose. -
source
/chore— This is the lane for changes with no behavior to test-drive — prose edits, a version bump on an -
source
/cleanup— {{SKILL_ENTRY:post-merge-cleanup}} -
source
/cleanup— Clean up an already-merged local branch after proving containment. Confirm each discard and preserve unique work. -
source
/cleanup— Run it from the merged topic branch; it takes no arguments, and the request alone never approves a discard. -
source
/commit— Create a verified local Git commit when committing changes is requested. Not for explaining commit history, drafting a message only, or postponing a commit. Applies every commit gate and never implies a push or PR. -
source
/commit— {{SKILL_ENTRY:commit-gate}} -
source
/commit— This is the single entry point for turning staged work into a commit — nothing in codeArbiter -
source
/conflict— Stop everything and surface a rule conflict — persona vs. docs vs. code. Present both sides and the conflict-hierarchy level; the user resolves. No silent reconciliation. -
source
/conflict— The protocol for a rule conflict — not a skill route, an orchestrator-level halt. When two sources -
source
/conflict— Stop everything and surface a rule conflict — persona vs. docs vs. code. Present both sides and the conflict-hierarchy level; the user resolves. No silent reconciliation. -
source
/context-check— Inspect context drift and refresh selected source-backed documents under existing authorization. -
source
/context-check— It takes no arguments and only reports drift until you select a refresh. -
source
/context-check— {{SKILL_ENTRY:context-check}} -
source
/create-context— {{SKILL_ENTRY:context-creation}} -
source
/create-context— Build source-backed project context through bounded inspection, optional agents, and record-level knowledge writes. -
source
/create-context— It takes no arguments and populates a repository that has source but no project context yet. -
source
/debug— A fixture command named debug, colliding with the debug skill/agent. -
source
/debug— Investigate an unexplained defect or unexpected behavior without changing application code. Use for root-cause diagnosis and an evidence-backed handoff, including a bounded unresolved result. Not for implementing a known fix, new features, or explanation-only questions. -
source
/debug— {{SKILL_ENTRY:debug}} -
source
/debug— `/ca:debug` investigates an unexplained symptom and returns a cited diagnosis or a bounded -
source
/decompose— Develop greenfield intent or initialized brownfield target and delta in existing decomposition and knowledge records. -
source
/decompose— {{SKILL_ENTRY:decompose}} -
source
/decompose— It takes no arguments and starts a resumable interview about what the project should become. -
source
/doctor— Proves the install is actually enforcing, rather than just present. codeArbiter's worst failure -
source
/doctor— Verify the active host install, package, command ownership, enforcement, and harmless live-fire probe. Read-only. -
source
/doctor— Verify the active host install, package, command ownership, enforcement{{IF:pi}}, wrapper self-test, and active-dispatch coverage gap{{ELSE}}, and harmless live-fire probe{{END}}. Read-only. -
source
/feature— Build an authorized feature from a maintained specification, testable criteria and useful plan, without duplicating user approval. -
source
/feature— The feature entry turns your requested outcome into testable criteria and a practical plan. -
source
/feature— Build an authorized feature from a maintained specification, testable criteria and useful plan, without duplicating user approval. -
source
/fix— Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates. -
source
/fix— Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates. -
source
/fix— This is the entry point for an authorized repair of a confirmed code defect. Give the observed -
source
/init— This is how a repository opts into codeArbiter for the first time. It writes the root-level state -
source
/init— Opt this repo into codeArbiter — scaffold the root-level .codearbiter/ state store. -
source
/init— Opt this repo into codeArbiter — scaffold the root-level .codearbiter/ state store. -
source
/override— Sanctioned, logged bypass of a gate or hard rule — one audit line, then proceed. -
source
/override— The sanctioned, logged escape hatch. A routine gate — a lint rule, a style check, a non-security -
source
/override— Sanctioned, logged bypass of a gate or hard rule — one audit line, then proceed. -
source
/pr— Explicit PR entry and a direct request to open a PR use the same branch-finishing owner. -
source
/pr— {{SKILL_ENTRY:finishing-a-development-branch}} -
source
/pr— Open a PR or finish branch disposition; route CI watching and post-merge cleanup to their owners. Merge and discard need explicit authority. -
source
/prune— A fixture command named prune, used to regression-test forge badges. -
source
/prune— Trim transcript clutter to extend session lifetime — analyze, prune a copy, or toggle the after-each-turn service. Dry-run by default; gains land at resume/compaction, not the current turn. -
source
/prune— Trim transcript clutter to extend session lifetime — analyze, prune a copy, or toggle the after-each-turn service. Dry-run by default; gains land at resume/compaction, not the current turn. -
source
/prune— This is a Feature Forge preview command — the after-each-turn service ships **off** by default and -
source
/reconcile— Compares architectural records with the scaffold and prior decisions using SMARTS. -
source
/reconcile— Inspect architectural variances with SMARTS; record only explicit user choices. Report-only requests make no changes. -
source
/reconcile— {{SKILL_ENTRY:decision-variance}} -
source
/refactor— This is the lane for moving or reshaping code without changing what it does — a rename, an extract, -
source
/refactor— {{SKILL_ENTRY:refactor}} -
source
/refactor— Restructure code without changing observable behavior: rename, extract, inline, move, deduplicate, or replace an internal implementation with an equivalent one. Prove parity through unchanged pre-existing tests. Not for new behavior, bug fixes, explanation-only questions, or committing finished work. -
source
/release— This is the only sanctioned way a version tag gets created, and it holds no knowledge of any -
source
/release— {{SKILL_ENTRY:release}} -
source
/release— Prepare a declared release target, or preview it with --dry-run. Derive its version and require authorization before publication. -
source
/review— A read-only review of the current change, dispatched by path against a reviewer-to-path matrix: -
source
/review— Review a diff with the reviewer fleet, funneled to one triaged verdict. Targets the current working diff, a path, or an inbound GitHub PR. -
source
/review— Review a diff with the reviewer fleet, funneled to one triaged verdict. Targets the current working diff, a path, or an inbound GitHub PR. -
source
/sample— A sample command for fixtures — single sanctioned path to a thing. -
source
/sandbox— Pull an untrusted repo into an ephemeral, host-FS-isolated Docker container — clone into a named volume, build a dep-cached image, run under structural isolation. Network defaults to offline. Requires Docker and nixpacks. -
source
/sandbox-cp— Copy a file OUT of a running sandbox box to the host — host-initiated egress only (docker cp). The reverse, a host→container bind, is impossible by construction. -
source
/sandbox-destroy— Tear down a sandbox box — remove its container and named volume. --keep-volume leaves the volume; with no id, prune reclaims any leaked ca.sandbox=1-labeled object. Cached images are retained. -
source
/sandbox-exec— Run a single command inside a running sandbox box and capture a JSON result — exitCode, separate stdout/stderr, and a truncated flag past the byte cap. The scriptable exec seam. -
source
/sandbox-shell— Open an interactive shell inside a running sandbox box at /work/repo. Read-only root, non-root user, no host-FS access — explore the untrusted code interactively, then exit. -
source
/spike— Exploratory spike on a throwaway branch — answer a named question with disposable code. Never merges; exits to a findings note or /ca:feature. -
source
/spike— This is the outlet for "I need to write code to find out" rather than "I know what to build." The -
source
/spike— Exploratory spike on a throwaway branch — answer a named question with disposable code. Never merges; exits to a findings note or {{CMD:feature}}. -
source
/sprint— Run an autonomous sprint from maintained specs and plans, with truthful verification and no duplicate artifact approval ceremonies. -
source
/sprint— Your sprint request establishes the working scope. codeArbiter maintains a specification and -
source
/sprint— Run an autonomous sprint from maintained specs and plans, with truthful verification and no duplicate artifact approval ceremonies. -
source
/standup— The daily hygiene checklist, made routine and gated: fetch and offer a fast-forward pull of the -
source
/standup— Daily repo hygiene — review the day's repo state, then perform selected cleanups. Fast-forward only, never destructive without a yes. -
source
/standup— Daily repo hygiene — review the day's repo state, then perform selected cleanups. Fast-forward only, never destructive without a yes. -
source
/status— Show the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only. -
source
/status— Show the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only. -
source
/status— A read-only snapshot of project maturity, pipeline progress, open tasks and questions, -
source
/statusline— Wire codeArbiter's statusline into ~/.claude/settings.json, or remove it. -
source
/statusline— Wires codeArbiter's renderer into `~/.claude/settings.json`, or removes it. A plugin can't own a -
source
/statusline— Wire codeArbiter's statusline into ~/.claude/settings.json, or remove it. -
source
/task— Add, select, start, complete, or reopen local work through its owning store. -
source
/task— Adds, selects, starts, completes or reopens local work through the one store that owns it. The -
source
/task— Add, select, start, complete, or reopen local work through its owning store. -
source
/threat-model— {{SKILL_ENTRY:security-architecture}} -
source
/threat-model— An opt-in, lightweight STRIDE pass over a design before it's built — invoked deliberately, never -
source
/threat-model— Threat-model a sensitive design with STRIDE on request. Read-only analysis of threats, controls, and implementation constraints. -
source
/tribunal— Tribunal is codeArbiter's deepest review, for a deliberate audit of a repository or subtree. -
source
/tribunal— Run an opt-in deep codebase audit with persisted findings. Confirm cost before dispatch; filing and telemetry need separate approval. -
source
/tribunal— {{SKILL_ENTRY:tribunal}} -
source
/watch— Watch a PR's CI to completion — diagnose on red, notify and offer the merge on green. Never auto-merges. -
source
/watch— Watch a PR's CI to completion — diagnose on red, notify and offer the merge on green. Never auto-merges. -
source
/watch— Watches a pull request's CI checks to completion without polling by hand. The wait is a real