chore command

Command

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

Invoke it

Claude Code/ca:chore

Codex$ca-chore

Pi/ca-chore

Availability is read from each shipped host catalog. Preview-only commands are marked on the page.

What it does

This is the lane for changes with no behavior to test-drive — prose edits, a version bump on an existing dependency, or backing out a named commit. Each of the three types gets exactly the checks it needs and nothing more: a docs edit gets a secrets scan and a copy pass instead of a demand for failing tests that would never exist for prose; a dependency bump gets the same vetting /ca:add-dep applies plus impact-bounded local tests; a revert has to be a real git revert, never a hand-edited backout, and also needs the affected regression tests green afterward. Exhaustive cross-platform proof remains mandatory in exact-head hosted CI before merge. Anything that smuggles in a behavioral code change gets redirected — this lane exists precisely to keep TDD ceremony off changes that have nothing to test.

Usage

/ca:chore <docs|deps|revert> <description or SHA>

Name the type first, then the docs description, the dependency to bump, or the commit SHA to revert.

Example

> /ca:chore deps bump lodash to 4.17.21

Classified: deps.
Dispatching dependency-reviewer... license MIT (unchanged), no new transitive risk, changelog reviewed.
Manifest and lockfile updated together.
Running affected dependency and contract tests... 42 passed, 0 failed.
Exhaustive exact-head GitHub Actions checks remain required before merge.
Routing to commit-gate (classification: chore)...

When to reach for it

Reach for /ca:chore for docs-only edits, an existing dependency’s version bump, or reverting a named commit. A brand-new dependency goes through /ca:add-dep first; any behavioral change goes through /ca:feature or /ca:fix.

Gates

Gate	When	Effect
type classification	before any gate runs	the request must sort cleanly into docs, deps, or revert; a behavioral change beyond that scope redirects to feature or fix
type-scaled checks	after classification	docs gets a copy pass and a secrets scan; deps gets dependency review plus affected tests; revert gets a clean git revert plus affected regression tests; exhaustive exact-head proof runs in hosted CI
commit-gate	after the type’s checks pass	the change still exits through the standard commit gate and lands via branch and PR

Route context

Find this entry in the workflow atlas. Compare its related teaching maps, host spelling and context inputs. The exact procedure below remains the owner.

Source

Source — plugins/ca/commands/chore.md (v3.7.0)

---
description: Sanctioned lane for non-behavioral work — docs-only edits, dependency bumps, reverts. Type-scaled gates; no TDD demanded of prose.
argument-hint: "<docs|deps|revert> <description or SHA>"
---

# /ca:chore — non-behavioral change lane

The sanctioned path for work that has no behavioral surface to test-drive. Three types, each with
the gates that fit it — and nothing it doesn't need. Everything still exits through `commit-gate`
(classification `docs` / `chore` / `revert`) and lands via branch/PR.

## Types

**docs** — README, comments, CHANGELOG, `.codearbiter/` prose, typo fixes.
- Gates: secrets scan over the diff; diff review (no behavioral code change smuggled in);
  anti-slop copy pass on any user-facing doc in the change; `commit-gate`.
- **Anti-slop copy pass** — for any user-facing doc the change touches (repo-root community docs
  and `docs/**`; not codeArbiter's own framework bodies), load
  `${CLAUDE_PLUGIN_ROOT}/includes/anti-slop-design/INDEX.md`, then `core.md` and the
  `medium-documents` leaf (§7.A.1), and run the §3.A em-dash ban and the §3.B copy self-audit over
  the authored prose before `commit-gate`. The `H-13` PostToolUse reminder surfaces §3.A separator
  dashes as you write, so the pass is a confirmation, not a discovery.
- No `tdd` — prose has no failing test to write.

**deps** — bump an existing dependency's version (manifest + lockfile together, never one without
the other).
- Gates: dispatch `dependency-reviewer` (same vetting as `/ca:add-dep` — license, provenance,
  supply chain, changelog of the bump); affected local tests green under
  `${CLAUDE_PLUGIN_ROOT}/includes/verification-boundary.md`; exhaustive exact-head hosted CI before merge;
  `commit-gate`.
- A bump that requires code changes to adopt is not a chore — route the code change through
  `/ca:feature` or `/ca:fix`.

**revert** — back out a named commit.
- Gates: `git revert <SHA>` (never hand-edited backout); affected local tests green under the shared
  `verification-boundary`, exhaustive exact-head hosted CI before merge; the
  commit message references the reverted SHA and the reason; `commit-gate`.
- No new regression test demanded — the revert restores already-tested behavior. If the revert is
  fixing a defect the suite missed, open `/ca:fix` afterward to pin it.

## Flow

1. Classify `$ARGUMENTS` into one of the three types. Anything with a behavioral code change beyond
   a mechanical revert is NOT a chore — redirect to `/ca:feature` or `/ca:fix` and stop.
2. Run the type's gates above.
3. Exit through `commit-gate` with the matching classification, then
   `finishing-a-development-branch` as usual.

## Hard gate

MUST reject a change containing behavioral code (beyond the revert itself) — that is `/ca:feature`
or `/ca:fix` territory. MUST keep manifest and lockfile changes in the same commit for `deps`.
MUST run impact-bounded local verification for `deps` and `revert` and require exhaustive exact-head
hosted CI before merge. MUST run the anti-slop copy pass on any user-facing
doc a `docs` change authors or edits. Never skips `commit-gate`.

## When NOT to use

- Any new or changed behavior → `/ca:feature` / `/ca:fix`.
- Adding a NEW dependency → `/ca:add-dep`.
- Restructuring code → `/ca:refactor`.

View in repo