Ca Debug Agent Skill

Investigate-then-decide root-cause analysis for a defect whose cause is unknown. No code changes — exits to $ca-fix, $ca-adr, or a no-action close.

569 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

138

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/arbiterForge/codeArbiter --skill ca-debug

The instruction itself

4 sections, as written by the author

$ca-debug — root-cause investigation

Investigates a defect, anomaly, or unexpected behavior whose cause is not yet known. Separates investigation from implementation: no code is modified while debugging. Describe the symptom with enough fidelity that another operator could reproduce it — observed behavior, reproduction steps (or intermittent-trigger profile), and environment. Vague descriptions ("it's flaky") are rejected; the orchestrator asks for clarification before routing.

If the cause is already known and a regression test is already named, invoke $ca-fix directly.

Routes to

The debug skill (${CLAUDE_PLUGIN_ROOT}/routines/debug/SKILL.md) — five gated phases: symptom

capture, hypothesis generation, evidence gathering, root-cause decision, handoff. Phase 4 forces one

named exit:

(a) Confirmed bug → $ca-fix, carrying the confirmed bug statement, cited evidence, and a named

regression test obligation tied to the minimal repro.

(b) Behavior/design ambiguity → $ca-adr, with the ambiguity statement and evidence ledger,

authored only with explicit user attribution.

(c) No-action close — symptom and rationale appended to

<project-root>/.codearbiter/open-tasks.md.

A real finding that is out of scope for those exits is marked inline [NEEDS-TRIAGE] and the

investigation continues.

When NOT to use

Known bug with a named regression test → $ca-fix directly.
Design discussion with no failing behavior → $ca-adr.
New feature → $ca-feature.
A general "why does it behave this way" question with no defect → $ca-btw.
Re-entry from inside $ca-fix or $ca-adr → exit that command first (routing-cycle prevention).

Hard gate

MUST NOT modify any code during Phases 1–5 — code changes belong to $ca-fix. MUST exit Phase 4 with

exactly one of (a)/(b)/(c). Exit (a) MUST carry a regression test obligation. Exit (b) MUST obtain

user attribution before any $ca-adr. MUST NOT promote INCONCLUSIVE evidence to CONFIRMED without a

cited source.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

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

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take arbiterforge/ca-debug from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.