cavecrew

Route code tasks to investigator, builder, or reviewer subagents.

199|41|Updated Oct 25, 2020
One-click install
npx skills add https://github.com/rvdbreemen/OTGW-firmware --skill cavecrew-rvdbreemen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cavecrew
Source: https://github.com/rvdbreemen/OTGW-firmware/tree/main/.agents/skills/cavecrew
Command: npx skills add https://github.com/rvdbreemen/OTGW-firmware --skill cavecrew-rvdbreemen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents context exhaustion during long coding sessions by helping you delegate investigation, small edits, and diff reviews to caveman-style subagents that return compressed tool results.

Core Features & Use Cases

  • Delegation decision guide: Chooses between cavecrew-investigator, cavecrew-builder, and cavecrew-reviewer based on task size, uncertainty, and desired output format.
  • Task-appropriate subagent routing: Uses investigation for “where/what calls” queries, builder for obvious ≤2-file surgical edits, and reviewer for structured diff findings with severity.
  • Output-efficiency strategy: Ensures tool results are returned in a compact contract so the main thread preserves more tokens over many delegations.

Example: When you ask “Where is the MQTT MsgID routing logic defined and what calls it?”, use cavecrew-investigator to get a grep-friendly file:line list, then hand 1–2 exact paths to cavecrew-builder for a targeted fix, and finally run cavecrew-reviewer to audit the resulting diff.

Quick Start

Tell the AI: “delegate to cavecrew for a compressed investigation of where X is defined, then review the diff for issues.”

Frequently Asked Questions about cavecrew

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

FAQPage Schema
How do I prevent context exhaustion during long coding sessions?

You can delegate code investigation and editing tasks to subagents that return compressed tool outputs, preventing context exhaustion. This preserves your main thread tokens by routing work to specialized agents that summarize findings and diffs efficiently.

What is the best way to delegate code investigation and diff review?

Use a delegation decision guide to route tasks to specialized subagents based on size and uncertainty. Assign investigators for locating definitions, builders for surgical edits, and reviewers for structured diff findings with severity levels.

How do I perform surgical code edits within a specific file scope?

Delegate the task to a builder subagent after providing exact file paths identified during investigation. The builder executes targeted changes while respecting the explicit file-scope limit, ensuring edits remain constrained to one or two files.

Can I get structured diff findings with severity levels for code changes?

Yes, you can delegate the review process to a reviewer subagent. It audits the resulting code diff and produces a structured report highlighting issues and their respective severity levels, ensuring changes are thoroughly evaluated.

When should I use subagent delegation for code navigation tasks?

Use subagent delegation for code navigation tasks when you need to locate definitions or callers without exhausting your main context. Delegating to an investigator subagent returns a compressed file and line list, saving tokens for subsequent work.

Does cavecrew require any external dependencies to manage agent orchestration?

No, cavecrew does not require external dependencies to manage agent orchestration. It operates as a standalone delegation decision guide that triggers on specific phrases to route tasks to investigation, builder, or reviewer subagents using compressed output contracts.