cavecrew

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

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill cavecrew-ferrarifankid04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cavecrew
Source: https://github.com/ferrarifankid04/ai-skills-public/tree/main/antigravity/caveman/plugins/caveman/skills/cavecrew
Command: npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill cavecrew-ferrarifankid04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Subagent tool results are injected verbatim into the main conversation context, so verbose agent output quickly exhausts the context window during long coding sessions. This Skill provides a decision guide for delegating work to three caveman-compressed subagents whose output is roughly 60% smaller, letting the main context last longer. ## Core Features & Use Cases - Delegation Decision Guide: A lookup table tells you when to spawn cavecrew-investigator (locate code), cavecrew-builder (1-2 file edits), or cavecrew-reviewer (diff review) versus using vanilla agents or the main thread. - Structured Output Contracts: Each subagent returns a predictable, greppable format with file paths, line numbers, and severity totals, so results are easy to parse and chain. - Chaining Patterns: Supports locate-fix-verify pipelines, parallel investigator scouting, and single-shot edits when the target site is already known. - Use Case: During a long refactoring session, spawn cavecrew-investigator to find all call sites of a function, hand the top two sites to cavecrew-builder for surgical edits, then have cavecrew-reviewer audit the diff, all while consuming a fraction of the context a vanilla agent would. ## Quick Start Ask the assistant to use cavecrew to delegate locating a function definition to the investigator subagent instead of running a vanilla Explore agent.

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 without wasting context?

Spawn cavecrew-investigator instead of a vanilla Explore agent. It returns file-path-first results with line numbers and backticked symbols in a compressed format, so the tool result injected into main context is about 60% smaller.

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 new features, three or more files, or cross-cutting refactors, do the work in the main thread or use a code architect agent, since the builder will return too-big for oversized tasks.

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

cavecrew-reviewer returns findings only, sorted by file and line with severity emoji and totals, in a compact format. A vanilla Code Reviewer provides deep rationale, architecture commentary, and alternatives, which costs more context but reads better for humans.

Can I run multiple cavecrew investigators in parallel?

Yes. The parallel scout pattern spawns two to three cavecrew-investigator calls in one message, each covering a different angle such as definitions, callers, or tests. You then aggregate the compressed results in the main thread.

When should I not use cavecrew subagents?

Avoid cavecrew when you need prose explanations, architecture opinions, or output a human will read directly, since the compressed format can be cryptic. Also skip the builder when you do not yet know the target file, and never chain investigator to builder for large multi-file refactors.