ca-checkpoint
Periodic multi-reviewer sweep of the whole codebase — surfaces a triaged checkpoint report.
npx skills add arbiterForge/codeArbiter --skill ca-checkpoint --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# $ca-checkpoint — codebase sweep Periodic sweep of the entire codebase with the reviewer fleet, funneled to a single dated report. Surfaces findings — not a promotion gate, enforces no sign-off. ## Flow 1. Build the unit list — the same fleet as `$ca-review`, scoped to the whole codebase against the `<project-root>/.codearbiter/` docs: | Reviewer | Reads | |---|---| | `security-reviewer` | `security-controls.md`; reviews security posture | | `auth-crypto-reviewer` | `security-controls.md`; authn/crypto/key/secret paths | | `dependency-reviewer` | dependency manifests; license + supply-chain posture | | `migration-reviewer` | migration history; safety + classification | | `coverage-auditor` | test coverage vs. obligations across the tree | | `architecture-drift-reviewer` | `decisions/`; drift between code and accepted ADRs | 2. Route to `dispatching-parallel-agents` with that unit list (read-only batch). It dedupes, then funnels through `finding-triage` → `checkpoint-aggregator`. 3. `checkpoint-aggregator` writes the dated report to `<project-root>/.codearbiter/checkpoints/YYYY-MM-DD.md`: findings by severity with file:line, and out-of-scope items marked inline `[NEEDS-TRIAGE]`. 4.
- Flow
- Hard gate
- When NOT to use
What does the ca-checkpoint skill do?
Periodic multi-reviewer sweep of the whole codebase — surfaces a triaged checkpoint report.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-checkpoint --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.