claude

ca

Assistive orchestration for Claude Code: maintain project context and plans, implement authorized work, coordinate useful reviews, and record actual checks and progress. Preserves host permissions, repository safeguards and audit history without a second artifact permission exchange. Requires Python 3 on PATH. Dormant until you opt a repo in; run /ca:init to activate.

153 on GitHubby arbiterForgev3.8.9AGPL-3.0-onlyupdated today
/

Plugin ca from marketplace codearbiter in arbiterForge/codeArbiter. Commands read from the repo's manifest — today.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (22)

  • brainstorming

    Refine feature and sprint intent into a useful specification. Capture scope, observable criteria and material choices without repeated artifact approval ceremonies.

  • commit-gate

    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.

  • context-check

    Inspect context drift and refresh selected source-backed documents under existing authorization.

  • context-creation

    Build source-backed project context through bounded inspection, optional agents, and record-level knowledge writes.

  • 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 list lives in securi

  • 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.

  • decision-lifecycle

    Record user-decided ADRs or inspect their health read-only. Preserve attribution and acceptance evidence.

  • decision-variance

    Inspect architectural variances with SMARTS; record only explicit user choices. Report-only requests make no changes.

  • decompose

    Develop greenfield intent or initialized brownfield target and delta in existing decomposition and knowledge records.

  • dispatching-parallel-agents

    Parallel fan-out for authors, scouts and reviewers. Collect every result; only explicit review batches use finding-triage and verdict-aggregator.

  • executing-plans

    Assistive /feature coordinator. Select relevant tasks from a maintained spec/plan, delegate a useful batch when warranted, record verified versus pending checks honestly, and give progress summaries without default human-approval stops.

  • finishing-a-development-branch

    Open a PR or finish branch disposition; route CI watching and post-merge cleanup to their owners. Merge and discard need explicit authority.

  • post-merge-cleanup

    Clean up an already-merged local branch after proving containment. Confirm each discard and preserve unique work.

  • 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

  • release

    Prepare a declared release target, or preview it with --dry-run. Derive its version and require authorization before publication.

  • 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, test fixture, erro

  • security-architecture

    Threat-model a sensitive design with STRIDE on request. Read-only analysis of threats, controls, and implementation constraints.

  • subagent-driven-development

    Assistive implementation engine for /sprint and scoped executing-plans work. Follow actual dependencies, implement or delegate coherently, run relevant checks, preserve honest evidence, and advance without artifact approval codes or compulsory reviewer cascades.

  • tdd

    Verify authorized feature, fix, and refactor work with scoped obligations, regression-first fixes, behavioral checks, characterization baselines, coverage, and lint.

  • tribunal

    Run an opt-in deep codebase audit with persisted findings. Confirm cost before dispatch; filing and telemetry need separate approval.

  • 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 each unit back onto the

  • writing-plans

    Turn the selected specification into a maintained implementation plan with clear outcomes, useful tasks, dependencies, and verification steps. Drafting uses the existing authorization and does not require artifact approval codes, reviewer receipts, or a frozen implementation script.

Slash commands (33)

  • /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

    Inspect ADR health read-only; optionally select one ADR with --adr N.

  • /ca:adr

    Record user-decided ADRs or inspect their health read-only. Preserve attribution and acceptance evidence.

  • /ca: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.

  • /ca:checkpoint

    Periodic multi-reviewer sweep of the whole codebase — surfaces a triaged checkpoint report.

  • /ca:chore

    Sanctioned lane for non-behavioral work — docs-only edits, dependency bumps, reverts. Type-scaled gates; no TDD demanded of prose.

  • /ca:cleanup

    Clean up an already-merged local branch after proving containment. Confirm each discard and preserve unique work.

  • /ca: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.

  • /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

    Inspect context drift and refresh selected source-backed documents under existing authorization.

  • /ca:create-context

    Build source-backed project context through bounded inspection, optional agents, and record-level knowledge writes.

  • /ca: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.

  • /ca:decompose

    Develop greenfield intent or initialized brownfield target and delta in existing decomposition and knowledge records.

  • /ca:doctor

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

  • /ca:feature

    Build an authorized feature from a maintained specification, testable criteria and useful plan, without duplicating user approval.

  • /ca:fix

    Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.

  • /ca:init

    Opt this repo into codeArbiter — scaffold the root-level .codearbiter/ state store.

  • /ca:override

    Sanctioned, logged bypass of a gate or hard rule — one audit line, then proceed.

  • /ca:pr

    Open a PR or finish branch disposition; route CI watching and post-merge cleanup to their owners. Merge and discard need explicit authority.

  • /ca: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.

  • /ca:reconcile

    Inspect architectural variances with SMARTS; record only explicit user choices. Report-only requests make no changes.

  • /ca: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

  • /ca:release

    Prepare a declared release target, or preview it with --dry-run. Derive its version and require authorization before publication.

  • /ca: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.

  • /ca:spike

    Exploratory spike on a throwaway branch — answer a named question with disposable code. Never merges; exits to a findings note or /ca:feature.

  • /ca:sprint

    Run an autonomous sprint from maintained specs and plans, with truthful verification and no duplicate artifact approval ceremonies.

  • /ca:standup

    Daily repo hygiene — review the day's repo state, then perform selected cleanups. Fast-forward only, never destructive without a yes.

  • /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.

  • /ca:statusline

    Wire codeArbiter's statusline into ~/.claude/settings.json, or remove it.

  • /ca:task

    Add, select, start, complete, or reopen local work through its owning store.

  • /ca:threat-model

    Threat-model a sensitive design with STRIDE on request. Read-only analysis of threats, controls, and implementation constraints.

  • /ca:tribunal

    Run an opt-in deep codebase audit with persisted findings. Confirm cost before dispatch; filing and telemetry need separate approval.

  • /ca:watch

    Watch a PR's CI to completion — diagnose on red, notify and offer the merge on green. Never auto-merges.

Subagents (21)

  • INDEX
  • 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.

  • authority-reviewer

    INTERNAL independent reviewer for structured-artifact spec and quality review on Claude Code. Launched only through an armed authority request's exact envelope; read-only; returns one review-decision JSON object. Never dispatch directly.

  • backend-author

    Implement backend/server-side code with scoped verification, input validation, framework conventions, and ORM usage. Reads tech stack from ${CLAUDE_PROJECT_DIR}/.codearbiter/tech-stack.md.

  • checkpoint-aggregator

    Persists a complete verdict-aggregator output under the selected dated checkpoint filename in .codearbiter/checkpoints/. Writer, 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 .codearbiter/decisions/.

  • 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) apply the reference in

  • finding-triage

    Post-processes reviewer reports — consolidates findings, classifies each by severity and whether it blocks the current change. Sequential. Produces a unified read-only triage report for the verdict-aggregator and explicit checkpoint persistence.

  • frontend-author

    Implement frontend/UI code with scoped verification, component conventions, state management, and UI security. 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 Tribunal to classify unresolved integration relationships from a bounded inventory packet. Read-only; files no findings.

  • map-structure

    Dispatched by Tribunal to classify unresolved structural relationships from a bounded inventory packet. Read-only; 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 to review one lens or independently verify a candidate. Reads its mandate under skills/tribunal/references/lenses/. Never dispatch directly.

  • verdict-aggregator

    Composes a complete finding-triage report into one structured in-memory verdict for the caller. Read-only; never persists a checkpoint or modifies project state.

Hooks (30)

  • SessionStart

    python "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.py"

  • SessionStart

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.py"

  • PreToolUse

    python "${CLAUDE_PLUGIN_ROOT}/hooks/pre-bash.py"

  • PreToolUse

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/pre-bash.py"

  • PreToolUse

    python "${CLAUDE_PLUGIN_ROOT}/hooks/pre-write.py"

  • PreToolUse

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/pre-write.py"

  • PreToolUse

    python "${CLAUDE_PLUGIN_ROOT}/hooks/pre-edit.py"

  • PreToolUse

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/pre-edit.py"

  • PreToolUse

    python "${CLAUDE_PLUGIN_ROOT}/hooks/pre-read.py"

  • PreToolUse

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/pre-read.py"

  • PreToolUse

    python "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-authority-hook.py"

  • PreToolUse

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-authority-hook.py"

  • PostToolUse

    python "${CLAUDE_PLUGIN_ROOT}/hooks/post-write-edit.py"

  • PostToolUse

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/post-write-edit.py"

  • PostToolUse

    python "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-authority-hook.py"

  • PostToolUse

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-authority-hook.py"

  • PostToolUseFailure

    python "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-authority-hook.py"

  • PostToolUseFailure

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-authority-hook.py"

  • SubagentStart

    python "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-authority-hook.py"

  • SubagentStart

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-authority-hook.py"

  • SubagentStop

    python "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-authority-hook.py"

  • SubagentStop

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-authority-hook.py"

  • UserPromptSubmit

    python "${CLAUDE_PLUGIN_ROOT}/hooks/prune-transcript.py"

  • UserPromptSubmit

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/prune-transcript.py"

  • UserPromptSubmit

    python "${CLAUDE_PLUGIN_ROOT}/hooks/prompt-submit.py"

  • UserPromptSubmit

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/prompt-submit.py"

  • PreCompact

    python "${CLAUDE_PLUGIN_ROOT}/hooks/prune-transcript.py"

  • PreCompact

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/prune-transcript.py"

  • PreCompact

    python "${CLAUDE_PLUGIN_ROOT}/hooks/prompt-submit.py"

  • PreCompact

    python -c "import sys; raise SystemExit(0 if sys.version_info[0] >= 3 else 1)" || python3 "${CLAUDE_PLUGIN_ROOT}/hooks/prompt-submit.py"

View source on GitHub codearbiter.dev

More from arbiterForge/codeArbiter

All 3 plugins →

Governance kernel for OpenAI Codex CLI: the generated codeArbiter governance surface plus enforcement hooks (persona injection, blocking pre-exec and pre-write gates, append-only audit trail), sharing one .codearbiter/ store with the Claude Code sibling plugin. Standalone: opt a repo in with ca-init; enforcement stays dormant until .codearbiter/CONTEXT.md carries 'arbiter: enabled'. Requires Python 3 and Codex >= 0.143.0. CI continuously verifies, through a real Codex host at 0.143.0 and 0.145.0, that the plugin installs, reads back enabled, and ships every hook script it declares; an advisory lane tracks npm latest for upstream drift. Hook FIRING - live persona injection and live blocks inside a turn - is verified by hand per release against docs/codex-parity-testing.md, because a turn needs a model and a provider credential cannot gate fork pull requests.

53 skills · 20 agents · hooks

153

Locally-hosted Codespace equivalent for codeArbiter. Pulls an untrusted repo into an ephemeral, isolated Docker container with no host-filesystem access and configurable egress, caches dependencies by content hash, then tears the box down. Requires Docker; uses installed nixpacks when available, with a generated-Dockerfile fallback.

2 skills · 5 commands

153

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

ecc

claudecodex

Harness-native ECC operator layer - 71 agents, 314 skills, 98 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses

200 skills · 98 commands · 71 agents · 1 MCP server · hooks

affaan-m/ECC 302,088

Automated code review for pull requests using multiple specialized agents with confidence-based scoring to filter false positives

1 command

anthropics/claude-code 155,476

agent-skills

claudecodex

Production-grade engineering skills covering every phase of software development: spec, plan, build, verify, review, and ship.

25 skills · 4 agents

addyosmani/agent-skills 116,782

Agentic QE (external: maintained in proffesor-for-testing/agentic-qe, pinned to v3.15.17): a quality-engineering fleet with 11 QE agents, 9 skills, 9 commands, the agentic-qe MCP server pinned to the plugin version, and the aqe-mod guard that refuses destructive operations on AQE learning data

9 skills · 9 commands · 11 agents · 1 MCP server

ruvnet/ruflo 81,589

Maintain ca?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins3 plugins