ca-fix
Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.
npx skills add arbiterForge/codeArbiter --skill ca-fix --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-fix — regression-first bug fix The only permitted entry to bug-fix work. No fix code is written before a regression test reproduces the defect and goes red for the right reason. Give the observed behavior and the expected behavior, plus a stack trace or reproduction when you have one. **Orientation:** if `.codearbiter/code-map.md` is present, read it before diagnosing — a coarse concern→path→role map that helps locate the defect. Absent is fine; it is read-on-demand. ## Flow Routes to the `tdd` skill, bug variant — Phase 1 is framed around confirming the defect, not building new behavior: 1. **Reproduce** the bug consistently. 2. **Locate the root cause** — the exact code path producing the wrong behavior. 3. **Write a regression test** that fails in the current state for the precise reason the bug causes (not an unrelated error). 4. **Confirm it's red for the right reason** — the failure message matches the described defect. Only then does `tdd` proceed: minimal fix to green, then the remaining `tdd` gates. The implementation agent (`backend-author`, `frontend-author`, or `infra-author`) is selected by where the bug lives. If the defect cannot be pinned by a failing test, ST
- Flow
- Routes to
- When NOT to use
- Hard gate
What does the ca-fix skill do?
Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-fix --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.