Sanctioned lane for non-behavioral work — docs-only edits, dependency bumps, reverts. Type-scaled gates; no TDD demanded of prose.
npx skills add https://github.com/arbiterForge/codeArbiter --skill ca-chore
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.
docs — README, comments, CHANGELOG, .codearbiter/ prose, typo fixes.
anti-slop copy pass on any user-facing doc in the change; commit-gate.
and docs/**; not codeArbiter's own framework bodies), load
<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.
tdd — prose has no failing test to write.deps — bump an existing dependency's version (manifest + lockfile together, never one without
the other).
dependency-reviewer (same vetting as /ca-add-dep — license, provenance,supply chain, changelog of the bump); full test suite green after the bump; commit-gate.
/ca-feature or /ca-fix.
revert — back out a named commit.
git revert <SHA> (never hand-edited backout); full suite green after the revert; thecommit message references the reverted SHA and the reason; commit-gate.
fixing a defect the suite missed, open /ca-fix afterward to pin it.
$ARGUMENTS into one of the three types. Anything with a behavioral code change beyonda mechanical revert is NOT a chore — redirect to /ca-feature or /ca-fix and stop.
commit-gate with the matching classification, thenfinishing-a-development-branch as usual.
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 the full suite for deps and revert. MUST run the anti-slop copy pass on any user-facing
doc a docs change authors or edits. Never skips commit-gate.
/ca-feature / /ca-fix./ca-add-dep./ca-refactor.Use when implementing any feature or bugfix, before writing implementation code
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
Rules for writing and reviewing tests in the Remotion repository. Use whenever adding, editing, or reviewing tests, especially for Studio UI, rendering, CLI, server, media, and cross-package changes, to prefer complete integration workflows over narrow helper tests and implementation details.
Patterns and pitfalls for the ONNX domain Attention operator (opset 23/24) CUDA implementation. Use when modifying the dispatch cascade in core/providers/cuda/llm/attention.cc, writing mask/bias CUDA kernels, debugging attention test routing, or adding features to the ONNX Attention op. NOT for contrib domain MultiHeadAttention/GroupQueryAttention.
> Translates a HuggingFace model into a prefill-only AutoDeploy custom model using reference custom ops, validates with hierarchical equivalence tests.
Translates a HuggingFace model into a prefill-only AutoDeploy custom model using reference custom ops, validates with hierarchical equivalence tests.
Generates Angular 17+ standalone components, configures advanced routing with lazy loading and guards, implements NgRx state management, applies RxJS patterns, and optimizes bundle performance. Use when building Angular 17+ applications with standalone components or signals, setting up NgRx stores, establishing RxJS reactive patterns, performance tuning, or writing Angular tests for enterprise apps.
Take arbiterforge/codearbiter-ca-chore from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.