Ca Spike Agent Skill
Exploratory spike on a throwaway branch — answer a named question with disposable code. Never merges; exits to a findings note or /ca-feature.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/arbiterForge/codeArbiter --skill ca-spikeThe instruction itself
4 sections, as written by the author/ca-spike — exploratory spike
The sanctioned lane for "I need to write code to find out." Spike code is disposable by contract:
it never merges, never PRs, and never becomes the implementation. What survives a spike is the
*answer*, written down — the code is burned.
Flow
- Name the question — a spike without a falsifiable question is just freelancing. Restate
$ARGUMENTS as the question the spike answers and the timebox (default: one session). STOP for
the user's confirmation.
- Branch — create
spike/<slug>from the current branch. All spike work stays on it. - Explore — no
tdd, no plan, no review fleet. Two rules survive even here: no secret leaves
the approved store, and no irreversible operation (prod data, destructive migration) runs from a
spike.
- Exit — exactly one of:
- Answered → write the findings to
<project-root>/.codearbiter/spikes/<slug>.md
(the question, what was tried, the answer, what it implies), then delete the branch. If the
answer warrants building, hand the findings to /ca-feature — the spike file seeds
brainstorming; the spike code is reference material, never the implementation.
- Timebox expired, no answer → record that too (a dead end is a finding), delete the branch.
Hard gate
MUST NOT merge or PR a spike/* branch — its only exits are a findings file and deletion. MUST NOT
copy spike code into an implementation branch wholesale; implementation re-enters through
/ca-feature and tdd. Secret-handling and irreversibility rules hold even in a spike. Commits on
a spike/* branch are exempt from commit-gate — the exemption is safe precisely because nothing
on the branch can ever land.
When NOT to use
- You already know what to build →
/ca-feature. - Diagnosing a defect →
/ca-debug(investigation with a structured exit). - A question answerable by reading code or docs →
/ca-btw.
Other skills for the same job
different authors, same section of the catalogue
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.
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
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).
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.
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
How to use it
Take arbiterforge/codearbiter-ca-spike 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.