cavecrew

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

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Sambhav242005/Major-Project --skill cavecrew-sambhav242005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cavecrew
Source: https://github.com/Sambhav242005/Major-Project/tree/main/.continue/skills/cavecrew
Command: npx skills add https://github.com/Sambhav242005/Major-Project --skill cavecrew-sambhav242005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long coding sessions exhaust the main context window because vanilla subagent results are injected back verbatim as verbose prose. This Skill decides when to delegate to caveman-compressed subagents so each delegation costs roughly one third of the tokens. ## Core Features & Use Cases - Decision Matrix: Maps task types to the right agent — cavecrew-investigator for locating code, cavecrew-builder for edits of 1-2 files, cavecrew-reviewer for diff review, or vanilla agents when prose and rationale are wanted. - Output Contracts: Defines exact structured formats each subagent returns (path:line findings, verified edit summaries, severity-tagged review findings) so the main thread can parse results reliably. - Chaining Patterns: Documents locate-fix-verify and parallel-scout workflows, plus anti-patterns to avoid wasted turns. - Use Case: During a long refactoring session, spawn an investigator to find all call sites of a function, hand the top two sites to the builder for a surgical edit, then have the reviewer audit the diff — all while keeping main-context usage minimal. ## Quick Start Ask the assistant to delegate code exploration to a cavecrew investigator subagent to save context before starting a multi-file investigation.

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 to save context?

Spawn cavecrew-investigator for tasks like finding definitions, callers, or usages of a symbol. It returns compressed path:line findings roughly one third the size of vanilla Explore output, preserving main context across many delegations.

When should I use cavecrew-builder versus editing in the main thread?

Use cavecrew-builder when the edit scope is obvious and touches at most two files with known paths. It refuses three or more files with a too-big response, so larger refactors belong in the main thread or a feature architect agent.

What is the difference between cavecrew-reviewer and a vanilla code reviewer?

cavecrew-reviewer returns one-line findings with severity emoji and totals, sorted by file and line. The vanilla Code Reviewer provides prose, rationale, and architecture commentary, which costs more context but suits deep reviews.

Can I override the model used by cavecrew subagents?

Yes, set CAVECREW_REVIEWER_MODEL, CAVECREW_BUILDER_MODEL, or CAVECREW_INVESTIGATOR_MODEL environment variables before launching. The override patches only the model line in the installed agent frontmatter, leaving the prompt body untouched.

When should I not use cavecrew subagents?

Avoid cavecrew-builder when you do not already know the target file, and avoid chaining investigator to builder for five-file refactors. Also skip cavecrew-reviewer for general feedback requests, since it returns findings only without architecture opinions.