cavecrew

Guides delegation of code tasks to compressed-output subagents for investigation, editing, and review.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/bittlinkm/claude-setup --skill cavecrew-bittlinkm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cavecrew
Source: https://github.com/bittlinkm/claude-setup/tree/main/skills/cavecrew
Command: npx skills add https://github.com/bittlinkm/claude-setup --skill cavecrew-bittlinkm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Subagent results are injected verbatim into the main conversation context, so verbose agent output quickly exhausts the context window during long sessions. This Skill tells the main thread when to delegate to caveman-compressed subagents instead of doing work inline or using vanilla agents, keeping each delegation's context cost small. ## Core Features & Use Cases - Delegation decision matrix: Maps task types to the right agent — cavecrew-investigator for locating code, cavecrew-builder for surgical 1-2 file edits, cavecrew-reviewer for diff review, or vanilla agents when prose and rationale are wanted. - Structured output contracts: Each subagent returns a compact, greppable format (path:line findings, one-line change summaries, severity-tagged review findings) instead of prose. - Chaining patterns: Supports locate → fix → verify pipelines, parallel investigator scouting, and single-shot edits when the site is already known. - Use Case: During a long debugging session, spawn cavecrew-investigator to find all callers of a function, hand the chosen site to cavecrew-builder for the fix, then have cavecrew-reviewer audit the diff — all while keeping main-context usage low. ## Quick Start Ask the assistant to delegate a code search to the cavecrew investigator subagent so the results come back in compressed form.

Frequently Asked Questions about cavecrew

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate code search to a subagent in Claude Code?

Use the cavecrew-investigator subagent for read-only code location tasks like finding definitions, callers, or usages. It returns a compressed path:line list with symbols and notes, which costs far less main-context budget than a vanilla Explore agent.

When should I use cavecrew subagents instead of vanilla Explore?

Use cavecrew when you want the subagent's output in roughly a third of the tokens, such as locating code or reviewing diffs. Use vanilla Explore or Code Reviewer when you want prose, architecture commentary, or rationale.

How do I override the model used by cavecrew subagents?

Set environment variables before launching Claude Code: CAVECREW_REVIEWER_MODEL, CAVECREW_BUILDER_MODEL, or CAVECREW_INVESTIGATOR_MODEL with values like sonnet or opus. The override patches only the model line in the installed agent frontmatter.

What are the limitations of the cavecrew-builder subagent?

cavecrew-builder only handles surgical edits to one or two files where the scope is already obvious. It refuses three-or-more-file refactors by returning too-big, so use the main thread or a code architect agent for cross-cutting changes.

Why does delegating to subagents reduce main context usage?

Subagent tool results are injected into the main context verbatim, so verbose prose output consumes the context budget permanently. Cavecrew subagents return compressed structured output, so each delegation costs fewer tokens across a long session.