# Delegate Coding Tasks With Cavecrew

Long coding sessions lose context when subagents return verbose results. Cavecrew guides Claude, Codex, and Claude Code toward compact investigator, builder, and reviewer agents.

## Install

```bash
npx skillstore add juliusbrussee/cavecrew
```

## Metadata

- Status: approved
- Slug: juliusbrussee-cavecrew
- Skillstore revision: r1
- Version status: missing
- Tree hash: d0a8c85f5533643b4c68c4550efd0e603cc78dc22c7c9ed6006bcecb0ff84ac7
- Author: juliusbrussee
- GitHub username: juliusbrussee
- License: MIT
- Repository: https://github.com/juliusbrussee/caveman/tree/main/skills/cavecrew/
- Ref: b8ca75d2c0a7e7102978993058777d82b8ab2610
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/juliusbrussee-cavecrew
- Manifest: https://skillstore.pages.dev/api/skills/juliusbrussee-cavecrew/manifest

## Capabilities

- Guides when to use cavecrew-investigator to locate definitions, callers, or usages.
- Guides when to use cavecrew-builder for clear edits in one or two files.
- Guides when to use cavecrew-reviewer for concise diff or file reviews.
- Compares cavecrew agents with vanilla Explore and Code Reviewer options.
- Defines output contracts and chaining patterns for locate, fix, and verify workflows.

## Use Cases

- Find Code References Quickly: Use the investigator agent when a developer needs concise file and line references before editing.
- Apply Small Focused Fixes: Use the builder agent when the scope is obvious and limited to one or two files.
- Review a Diff Efficiently: Use the reviewer agent when a team wants compact bug findings without extended commentary.

## Prompt Templates

### Choose the Right Cavecrew Agent

```
Use cavecrew to decide whether this task needs investigator, builder, reviewer, or the main thread: [describe task].
```

### Locate Code Before Editing

```
Use cavecrew-investigator to find where [symbol or behavior] is defined and where it is used. Return compact file and line references.
```

### Make a Small Verified Edit

```
Use cavecrew-builder for this focused change in [file or files]: [specific change]. Keep the edit limited and verify the result.
```

### Chain Locate Fix Review

```
Use cavecrew to locate the issue, apply a one or two file fix if the scope is clear, then review the diff for regressions.
```

## Limitations

- It is a decision guide, not an executable tool by itself.
- It depends on the referenced cavecrew subagents being installed and available.
- It favors compressed output, so details and rationale may be sparse.
- It is not suited to broad features, large refactors, or architecture discussions.

## Best Practices

- Use investigator before builder when the target file is not already known.
- Keep builder requests limited to one or two clear files.
- Use vanilla review agents when you need rationale, alternatives, or architecture advice.

## Anti Patterns

- Do not use builder for broad features or cross-cutting refactors.
- Do not ask reviewer for general feedback when you need design commentary.
- Do not use cavecrew when a direct one-line answer is already enough.

## Security Audit

- Audited at: 2026-07-06T18:00:06.927\+00:00
- Summary: Manual review found that the static findings are false positives from Markdown syntax. README.md uses relative links to repository documentation, and SKILL.md uses backticks and code fences for agent names and output contracts. No prompt injection, command execution, or path traversal behavior was found.

## Stats

- Views: 55
- Downloads: 6
- Favorites: 0
- Popularity score: 0