caveman-explore

Locates relevant code in repositories and returns path:line citations only.

1|Updated Aug 31, 2026
One-click install
npx skills add https://github.com/nguyenhungtran18/skill-and-tool-tracker --skill caveman-explore-nguyenhungtran18
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-explore
Source: https://github.com/nguyenhungtran18/skill-and-tool-tracker/tree/main/skills/caveman-explore
Command: npx skills add https://github.com/nguyenhungtran18/skill-and-tool-tracker --skill caveman-explore-nguyenhungtran18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agent faces a cold-start codebase or a failed direct search, it wastes tokens reading files one by one. This Skill performs broad, parallel read-only exploration and reports only where the relevant code lives, keeping exploration reads out of the main context. ## Core Features & Use Cases - Parallel Broad Search: Fans out Glob, Grep, and Read calls in a single turn to cover complementary hypotheses about where code lives. - Citation-Only Output: Returns a compact evidence block of path:START-END lines with short relevance reasons, never editing files or proposing solutions. - Honest Fallback: Replies with "no relevant locations found" instead of guessing when nothing relevant exists. - Use Case: A solver agent needs to know where route selection logic lives in an unfamiliar Go project. Delegate the question, and receive citations like src/router/pick.go:42-71 without polluting the solver's token budget. ## Quick Start Ask the explorer to find where the authentication middleware is defined in this repository and return only file paths with line ranges.

Frequently Asked Questions about caveman-explore

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

FAQPage Schema
How do I find where code lives in an unfamiliar repository?▼

Delegate a localization question to the explorer, which issues parallel Glob, Grep, and Read calls to cast a broad net. It returns a compact list of file paths with line ranges and short relevance reasons, without editing anything.

How to search a codebase without consuming the main agent's context?▼

Use a read-only sub-agent explorer whose file reads stay out of the main context. The solver receives only the final citation block, so large file contents never enter its token budget.

When should I not use a repository exploration agent?▼

Skip it when the exact file or symbol is already named, since direct reading is faster. The explorer is designed for cold-start orientation, broad cross-file localization, or cases where a direct search already failed.

Can the explorer modify files or run commands?▼

No. It is strictly read-only, using only Read, Glob, and Grep tools. It never edits files, executes commands, or proposes solutions; it only reports where relevant code lives.

What happens when code search finds no relevant locations?▼

The explorer replies with the single line "no relevant locations found" rather than guessing. It only cites line ranges it actually read and never invents or estimates ranges past the end of a file.