caveman--caveman-explore

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

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/hhenrichsen/dots --skill caveman-caveman-explore-hhenrichsen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman--caveman-explore
Source: https://github.com/hhenrichsen/dots/tree/main/dot_skills/caveman/caveman-explore
Command: npx skills add https://github.com/hhenrichsen/dots --skill caveman-caveman-explore-hhenrichsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agent or developer faces an unfamiliar codebase, finding where relevant logic lives wastes tokens and time. This Skill performs fast, read-only repository exploration and reports only file paths with line ranges, keeping its search activity out of the main context window. ## 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, citing only line ranges actually read. - Honest Fallback: Reports "no relevant locations found" rather than guessing when nothing relevant exists. - Use Case: A solver agent needs to know where route selection happens in a Go project. It delegates the question, and this Skill replies with citations like src/router/pick.go:42-71, letting the solver read only what matters. ## Quick Start Ask the explorer to find where a specific feature or symbol is implemented in this repository and return the file paths with line ranges.

Frequently Asked Questions about caveman--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 an unfamiliar codebase?▼

Delegate a localization question to this read-only explorer. It runs parallel Glob, Grep, and Read searches across the repository and replies with a compact list of file paths and line ranges showing where the relevant code lives.

What is the best way to search a repository without filling the context window?▼

Use a delegated read-only explorer whose searches stay out of the main context. It returns only path:line citations, so the main agent reads just the cited ranges instead of every file touched during the search.

When should I not use a repository exploration agent?▼

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

Can a read-only code explorer modify or run files in the repository?▼

No. This explorer never edits files, runs commands, or proposes solutions. Its only job is locating relevant code and reporting file paths with line ranges as an evidence block.

What happens when repository search finds no relevant code locations?▼

The explorer replies with the single line "no relevant locations found" instead of guessing. An honest empty answer is preferred over fabricated citations, since the consuming agent relies entirely on the accuracy of the list.