ca-chore
Sanctioned lane for non-behavioral work — docs-only edits, dependency bumps, reverts. Type-scaled gates; no TDD demanded of prose.
npx skills add arbiterForge/codeArbiter --skill ca-chore --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-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 wit
- Types
- Flow
- Hard gate
- When NOT to use
What does the ca-chore skill do?
Sanctioned lane for non-behavioral work — docs-only edits, dependency bumps, reverts. Type-scaled gates; no TDD demanded of prose.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-chore --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.