explore
Skill68 starsChanged 4 months agoMITView on GitHub
Deep codebase exploration to answer specific questions
69 other projects use a version of this.
Adopted by
Most recently taken up by
- Atmoskun/claude-skillstheir own version, first seen Nov 16, 2026
- timursafiullin/aodtheir own version, first seen Nov 15, 2026
- Renozoic-Foundry/forge-publictheir own version, first seen Nov 15, 2026
- lumpcode/lumpcodetheir own version, first seen Nov 14, 2026
- iwe-org/dev-workspacetheir own version, first seen Nov 14, 2026
- jskswamy/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
parcadeiSkillagentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +10 more from parcadei
Other versions69 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 69
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- JordanCoin/codemap★ 715same name
- ZimoLiao/scholaraio★ 589same name
- strands-agents/box★ 547same name
- andreasmolnardev/dashwise-next★ 465same name
- ai-analyst-lab/ai-analyst★ 304same name
- exmergo/dex★ 132same name
- striderZA/OpenCodeGameStudios★ 124same name
59 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 60 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
After exploration results: reflect on completeness, identify gaps
- Distinctive: line 16
Before answering: consider multiple interpretations, ensure accuracy
- Distinctive: line 32
Use AskUserQuestion if the question could have multiple interpretations:
- Distinctive: line 37
If question is clear and specific, skip to section 2.
- Distinctive: line 48
No ceiling, real floor: Use at least 2 agents per domain the question touches (1 only for a genuinely trivial single-file lookup).
- Distinctive: line 73
After agents return, verify coverage:
- Very specific: line 76
Similar patterns identified?: Do I have a reference implementation?
- Very specific: line 77
Data model complete?: If not -> launch additional parallel explore-db agents
- Very specific: line 78
Library docs sufficient?: If not -> launch additional parallel explore-docs agents
- Distinctive: line 115
CITE: - always reference file:line
- Distinctive: line 116
READ-ONLY: - do not modify anything
“Common” is measured: kept by at least 6 in 10 of the 60 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
YOU ARE EXECUTING THE /explore SKILL. The user triggered this skill. Follow ALL instructions below step by step. Do NOT treat this as a freeform conversation - execute the skill workflow.
Read-only exploration task.
Ultra Think Strategy
Ultra think before answering:
- After exploration results: reflect on completeness, identify gaps
- Before answering: consider multiple interpretations, ensure accuracy
- Cross-reference findings from different sources
1. PARSE QUESTION
Extract from $ARGUMENTS:
- Key terms and concepts to search
- Whether backend, frontend, or both
- Whether external documentation is needed
1.5 CLARIFY IF AMBIGUOUS
Use AskUserQuestion if the question could have multiple interpretations:
- "How does X work?" -> Which layer? What aspect?
- "Where is X handled?" -> At which level?
- "Find X" -> Find what exactly? (usage/definition/all)
If question is clear and specific, skip to section 2.
2. EXPLORE (PARALLEL)
Launch focused agents in a single message (parallel execution). There is no upper limit on agent count: one agent per distinct angle, scaling up with the question's breadth. The lists below are a starting menu, not a quota.
Agent-count principle
- You decide the count from the actual scope. Assess how many distinct concerns / areas / file-clusters the question really spans, and launch one focused agent for each. Do not anchor to a fixed number or to file counts.
- No ceiling, real floor. Use at least 2 agents per domain the question touches (1 only for a genuinely trivial single-file lookup). Above that floor there is no maximum.
- One distinct focus per agent. Split by angle so two agents never run the same search.
- No batching. Launch them all in one message.
Backend (one per distinct angle, no maximum):
explore-codebase: "Find [keywords] definitions and core logic in backend/internal/domain/ and backend/internal/application/"explore-codebase: "Find [keywords] implementations and usage in backend/internal/infrastructure/ and backend/internal/presentation/"explore-codebase: "Find similar patterns to [keywords] in backend/ for comparison"
Frontend (one per distinct angle, no maximum):
explore-codebase: "Find [keywords] components and hooks in frontend/src/components/ and frontend/src/hooks/"explore-codebase: "Find [keywords] types, API calls, and pages in frontend/src/types/, frontend/src/lib/, and frontend/src/app/"explore-codebase: "Find similar patterns to [keywords] in frontend/src/ for comparison"
Supporting (each fans out the same way, one per distinct concern, no maximum):
- Database:
explore-db- "[env] - [tables/schema question]" (one per table cluster / env) - Library:
explore-docs- "[library] [feature]" (one per library / feature) - External:
websearch- "[topic]" (one per topic)
For simple single-file lookups, 1 agent per domain is sufficient.
2.5 POST-EXPLORATION CHECK
After agents return, verify coverage:
- Full code path traced? Can I trace the complete flow? If gaps -> launch targeted
explore-codebase - Similar patterns identified? Do I have a reference implementation? If not -> launch
explore-codebase - Data model complete? If not -> launch additional parallel
explore-dbagents - Library docs sufficient? If not -> launch additional parallel
explore-docsagents
3. ANSWER
Provide comprehensive response:
## Answer
[Direct answer to the question]
## Evidence
### Code Found
- `path/to/file.ts:XX` - [description]
- `path/to/file.go:YY` - [description]
### Patterns Identified
- [Pattern 1]: [explanation]
### Documentation (if explore-docs used)
- [Library]: [relevant info]
### External Sources (if websearch used)
- [Title](URL) - [what we learned]
## Recommendations (if applicable)
- [Suggestion based on findings]Rules
- PARALLEL - launch relevant agents in ONE message
- CITE - always reference file:line
- READ-ONLY - do not modify anything
- THOROUGH - gather complete context before answering
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

