Ca Fix Agent Skill
Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/arbiterForge/codeArbiter --skill ca-fixThe instruction itself
5 sections, as written by the author$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:
- Reproduce the bug consistently.
- Locate the root cause — the exact code path producing the wrong behavior.
- Write a regression test that fails in the current state for the precise reason the bug causes
(not an unrelated error).
- 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, STOP and surface the question.
Routes to
tdd (${CLAUDE_PLUGIN_ROOT}/routines/tdd/SKILL.md) — all phases, Phase 1 framed for bug confirmation.
When NOT to use
- New behavior →
$ca-feature. - A behavior-preserving restructure →
$ca-refactor. - "Why does it do this?" →
$ca-btw. - Persisting fix code already written →
$ca-commit(the gates still apply).
Hard gate
MUST NOT write fix code before the regression test is red for the right reason. MUST NOT accept a test
that passes against the broken state as proof of the defect.
Other skills for the same job
different authors, same section of the catalogue
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
How to use it
Take arbiterforge/ca-fix 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.