caveman-explore

Locates relevant code in repositories and returns path:line citations via parallel read-only searches.

1|Updated May 3, 2021
One-click install
npx skills add https://github.com/leogurja/dotfiles --skill caveman-explore-leogurja
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-explore
Source: https://github.com/leogurja/dotfiles/tree/main/home/dot_agents/skills/caveman-explore
Command: npx skills add https://github.com/leogurja/dotfiles --skill caveman-explore-leogurja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agent or developer faces an unfamiliar codebase, finding where relevant logic lives burns context tokens and time. This Skill acts as a delegated, read-only explorer that answers localization questions with precise file and line citations, keeping bulky reads out of the main conversation context. ## Core Features & Use Cases - Parallel Broad Search: Issues Glob, Grep, and Read calls simultaneously in the first turn to cover complementary hypotheses instead of probing files one at a time. - Citation-Only Output: Returns a compact evidence block of path:START-END lines with relevance reasons, with no preamble, summaries, or proposed solutions. - Honest Fallback: Reports "no relevant locations found" rather than guessing when nothing matches, and never cites line ranges it did not actually read. - Use Case: A solver agent needs to know where route selection happens in a large Go service. It delegates the question, and this Skill replies with citations like src/router/pick.go:42-71 plus the covering test file, letting the solver read only what matters. ## Quick Start Ask the explorer where a specific feature or symbol is implemented in this repository and use the returned path:line citations to read only those locations.

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 a feature is implemented in a large codebase?▼

Delegate the localization question to a read-only explorer that fans out Glob, Grep, and Read calls in parallel. It returns path:line citations so you only read the relevant sections instead of scanning the whole repository.

How to search a repository without filling the agent context with file contents?▼

Use a sub-agent explorer whose reads stay out of the main context. It returns only a compact evidence block of file paths with line ranges, so the main agent's token budget is spent on solving, not searching.

When should I use a repository explorer instead of a direct grep?▼

Use it for cold-start orientation, broad cross-file questions, or after a direct search failed. Skip it when you already know the exact file or symbol name, since a direct read is faster.

Can the explorer edit files or run commands while searching?▼

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 the search finds nothing relevant in the repository?▼

The explorer replies with the single line "no relevant locations found" instead of guessing. It also never cites line ranges it did not actually read, so every citation is verified against the file.