Claude commands

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

{{SKILL_ENTRY:tribunal}}

{{SKILL_ENTRY:security-architecture}}

The sanctioned task-board mutator — add a queued task, start one (flips to in-progress and stamps the date, minting a dotted ID on pick-up), or mark an in-progress task done. The only blessed write to open-tasks.md.

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

Show the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only.

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.

Autonomous sprint — one interactive spec gate, then plan-to-PR execution with every auto-decision SMARTS-scored and logged. Hard gates remain true stops.

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

Review a diff with the reviewer fleet, funneled to one triaged verdict. Targets the current working diff, a path, or an inbound GitHub PR.

{{SKILL_ENTRY:release}}

{{SKILL_ENTRY:refactor}}

{{SKILL_ENTRY:decision-variance}}

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.

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_ENTRY:finishing-a-development-branch}}

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

Read-only 3-metric governance glance — override rate, small-lane rate, sprint low-confidence ratio — each with a trend arrow vs. the prior 20-commit window.

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

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

Start a feature: brainstorm a spec, get it approved, then drive it test-first through the pipeline. The one entry to implementation.

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.

{{SKILL_ENTRY:decompose}}

{{SKILL_ENTRY:debug}}