/ca-preview
Zero-onboarding, read-only dry-run of the reviewer fleet against the current uncommitted diff. Predicts reviewers, runs the state-free secret scan, writes nothing.
$ npx -y skills add arbiterForge/codeArbiter --skill ca-preview --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-preview
Context preview
The summary Claude sees to decide when to auto-load this skill.
Zero-onboarding, read-only dry-run of the reviewer fleet against the current uncommitted diff. Predicts reviewers, runs the state-free secret scan, writes nothing.
SKILL.md
ca-preview.SKILL.mdname: ca-preview
description: Zero-onboarding, read-only dry-run of the reviewer fleet against the current uncommitted diff. Predicts reviewers, runs the state-free secret scan, writes nothing.
argument-hint: (none)
$ca-preview — reviewer-fleet dry-run
See what codeArbiter would do to your real code before paying any onboarding cost. This is a read-only dry-run against the current uncommitted diff: it predicts which reviewers the change would dispatch, runs the checks that need no project rules, and reports. It never writes state.
It requires no `$ca-init`, no `.codearbiter/` directory, and no decompose or create-context interview. It functions in a repo that never opted in, and it modifies nothing: not the worktree, not the index, not `.codearbiter/`. `git status` is unchanged by a run.
Flow
1. **Collect the diff.** Call the thin entry hook `preview.py` in `diff` mode, which wraps `collect_diff` from `${CLAUDE_PLUGIN_ROOT}/hooks/_previewlib.py`. It unions HEAD-vs-worktree changes, staged changes, and untracked files (forward-slash paths). Run it from the project root so `_previewlib`/`_hooklib` resolve on the same `sys.path`:
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/preview.py" diff || python "${CLAUDE_PLUGIN_ROOT}/hooks/preview.py" diffIf the result is empty (clean tree, or not a git repo), print a friendly **"Nothing to preview"** line and STOP. This is a clean exit, not an error: no stack trace, no failure.
2. **Predict reviewers by path.** Read the reviewer-to-path matrix at `${CLAUDE_PLUGIN_ROOT}/includes/review-matrix.md`. That include is the single source of truth for which reviewer is dispatched when scope touches a given path: do NOT restate, fork, or inline a second copy of the table here. For each changed path, list the reviewers that WOULD dispatch and name the triggering path for each. This is the same mapping `$ca-review` uses, so the predicted set matches what a real review would dispatch.
3. **Run the state-free secret scan.** Call the thin entry hook `preview.py` in `secrets` mode, which wraps `scan_secrets` from `${CLAUDE_PLUGIN_ROOT}/hooks/_previewlib.py`. It reads each changed file's current content and returns `SecretFinding(path, line_no, snippet)` for every credential line, with the secret VALUE already masked to `****` in `snippet`:
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/preview.py" secrets || python "${CLAUDE_PLUGIN_ROOT}/hooks/preview.py" secretsReport each finding by `path:line_no` with its redacted snippet. The snippet arrives already masked: never reconstruct or print a raw secret value.
Report
Emit one clear report with these parts:
- **Changed files** — the reviewed-file set from step 1, each with its change kind(s) (unstaged,
staged, untracked).
- **Predicted reviewers** — per the matrix, which reviewers would dispatch and the triggering path
for each. These are predicted (would-dispatch), not run here.
- **Secret findings** — the results of the real scan from step 3, by `path:line_no` with the
redacted snippet, marked as found (ran locally), at BLOCK severity. State "none found" when the scan is clean.
- **Onboarding nudge** — close with one line: the full gated review comes via `$ca-init` then
`$ca-review`.
Distinct from $ca-doctor
This reports reviewer and gate behavior on the current diff. It makes NO hook-probe claims and says nothing about whether the install's hooks fire: that is `$ca-doctor`. Do not blend the two.
When NOT to use
- An onboarded repo wanting the full gated verdict → `$ca-init` then `$ca-review`.
- Proving the install's hooks actually fire → `$ca-doctor`.
- A question about the code → `$ca-btw`.
Hard gate
- Read-only. MUST NOT write, create, or modify any file, including anything under `.codearbiter/`;
MUST NOT stage or commit. `git status` MUST be unchanged after a run.
- MUST NOT require, trigger, or error on missing `$ca-init`, `.codearbiter/` state, or the
decompose / create-context interview.
- MUST NOT print a raw secret value: the lib returns the snippet already redacted, and the report
carries only that masked form.
- An empty diff or a non-git directory MUST yield the "Nothing to preview" message and a clean
exit, never a stack trace.
- MUST treat the reviewer prediction as predicted (would-dispatch) and the secret scan as found
(ran locally): it MUST NOT attribute fabricated findings to any predicted reviewer.
Read more
name: ca-preview description: Zero-onboarding, read-only dry-run of the reviewer fleet against the current uncommitted diff. Predicts reviewers, runs the state-free secret scan, writes nothing. argument-hint: (none)
$ca-preview — reviewer-fleet dry-run
See what codeArbiter would do to your real code before paying any onboarding cost. This is a read-only dry-run against the current uncommitted diff: it predicts which reviewers the change would dispatch, runs the checks that need no project rules, and reports. It never writes state.
It requires no `$ca-init`, no `.codearbiter/` directory, and no decompose or create-context interview. It functions in a repo that never opted in, and it modifies nothing: not the worktree, not the index, not `.codearbiter/`. `git status` is unchanged by a run.
Flow
1. **Collect the diff.** Call the thin entry hook `preview.py` in `diff` mode, which wraps `collect_diff` from `${CLAUDE_PLUGIN_ROOT}/hooks/_previewlib.py`. It unions HEAD-vs-worktree changes, staged changes, and untracked files (forward-slash paths). Run it from the project root so `_previewlib`/`_hooklib` resolve on the same `sys.path`:
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/preview.py" diff || python "${CLAUDE_PLUGIN_ROOT}/hooks/preview.py" diffIf the result is empty (clean tree, or not a git repo), print a friendly **"Nothing to preview"** line and STOP. This is a clean exit, not an error: no stack trace, no failure.
2. **Predict reviewers by path.** Read the reviewer-to-path matrix at `${CLAUDE_PLUGIN_ROOT}/includes/review-matrix.md`. That include is the single source of truth for which reviewer is dispatched when scope touches a given path: do NOT restate, fork, or inline a second copy of the table here. For each changed path, list the reviewers that WOULD dispatch and name the triggering path for each. This is the same mapping `$ca-review` uses, so the predicted set matches what a real review would dispatch.
3. **Run the state-free secret scan.** Call the thin entry hook `preview.py` in `secrets` mode, which wraps `scan_secrets` from `${CLAUDE_PLUGIN_ROOT}/hooks/_previewlib.py`. It reads each changed file's current content and returns `SecretFinding(path, line_no, snippet)` for every credential line, with the secret VALUE already masked to `****` in `snippet`:
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/preview.py" secrets || python "${CLAUDE_PLUGIN_ROOT}/hooks/preview.py" secretsReport each finding by `path:line_no` with its redacted snippet. The snippet arrives already masked: never reconstruct or print a raw secret value.
Report
Emit one clear report with these parts:
- **Changed files** — the reviewed-file set from step 1, each with its change kind(s) (unstaged,
staged, untracked).
- **Predicted reviewers** — per the matrix, which reviewers would dispatch and the triggering path
for each. These are predicted (would-dispatch), not run here.
- **Secret findings** — the results of the real scan from step 3, by `path:line_no` with the
redacted snippet, marked as found (ran locally), at BLOCK severity. State "none found" when the scan is clean.
- **Onboarding nudge** — close with one line: the full gated review comes via `$ca-init` then
`$ca-review`.
Distinct from $ca-doctor
This reports reviewer and gate behavior on the current diff. It makes NO hook-probe claims and says nothing about whether the install's hooks fire: that is `$ca-doctor`. Do not blend the two.
When NOT to use
- An onboarded repo wanting the full gated verdict → `$ca-init` then `$ca-review`.
- Proving the install's hooks actually fire → `$ca-doctor`.
- A question about the code → `$ca-btw`.
Hard gate
- Read-only. MUST NOT write, create, or modify any file, including anything under `.codearbiter/`;
MUST NOT stage or commit. `git status` MUST be unchanged after a run.
- MUST NOT require, trigger, or error on missing `$ca-init`, `.codearbiter/` state, or the
decompose / create-context interview.
- MUST NOT print a raw secret value: the lib returns the snippet already redacted, and the report
carries only that masked form.
- An empty diff or a non-git directory MUST yield the "Nothing to preview" message and a clean
exit, never a stack trace.
- MUST treat the reviewer prediction as predicted (would-dispatch) and the secret scan as found
(ran locally): it MUST NOT attribute fabricated findings to any predicted reviewer.
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

