cavecrew

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

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/marketiv-id/marketiv-web --skill cavecrew-marketiv-id
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cavecrew
Source: https://github.com/marketiv-id/marketiv-web/tree/main/.qwen/skills/cavecrew
Command: npx skills add https://github.com/marketiv-id/marketiv-web --skill cavecrew-marketiv-id

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 tells the main thread 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 surgical 1-2 file edits, cavecrew-reviewer for diff audits, or vanilla agents when prose and rationale are needed. - Output Contracts: Defines exact structured formats each subagent returns (path:line findings, verified edit confirmations, severity-tagged review findings) so the main thread can parse results reliably. - Chaining Patterns: Documents locate → fix → verify workflows, parallel investigator scouting, and single-shot edits. - Use Case: During a long refactoring session, spawn cavecrew-investigator to find all call sites of a function, hand the top two paths to cavecrew-builder for the edit, then have cavecrew-reviewer audit the diff — all while keeping main-context usage minimal. ## Quick Start Ask the assistant to delegate code investigation to a cavecrew investigator subagent to save context before starting a multi-file task.

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 with a locate query such as where a symbol is defined or what calls it. It returns a compressed path:line list instead of prose, so the tool-result injected into main context is roughly one third the size of a vanilla Explore result.

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

Use cavecrew-builder for surgical edits of one to two files where the scope is already obvious. For three or more files or cross-cutting refactors, use the main thread or a feature architect agent, since the builder refuses oversized scope with a too-big response.

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, with no architecture commentary. Use the vanilla Code Reviewer when you need rationale, alternatives, and prose explanations.

Can I change which model the cavecrew subagents use?

Yes. Set CAVECREW_REVIEWER_MODEL, CAVECREW_BUILDER_MODEL, or CAVECREW_INVESTIGATOR_MODEL environment variables before launching Claude Code. The override patches only the model line in the installed agent frontmatter.

When should I not use cavecrew subagents?

Avoid cavecrew when you want prose, architecture commentary, or rationale, when the answer is a one-liner you already know, or when handing builder a multi-file refactor. Compressed output can be cryptic if a human will read it directly.