explore-codebase
Skill1 starsChanged 24 days agoMITView on GitHub
Explore repository structure, locate symbol definitions, and trace call graphs without loading large files into context. Triggers on: explore codebase, find symbol, navigate code, locate function, map repository.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- rpraharaj/ai-sdlctheir own version, first seen Nov 1, 2026
- rpraharaj/ai-engineertheir own version, first seen Nov 1, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- Arasz/ai-badgertheir own version, first seen Oct 11, 2026
- johanolofsson72/Claudetheir own version, first seen Oct 2, 2026
- aprameyak/coding-skillstheir own version, first seen Oct 2, 2026
Used with
Projects with it also use review-changes, incident-triage and 2 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.
DockerSkillreview-changes
Review uncommitted or recently committed documentation changes for correctness, coherence, and style compliance. Use before creating a PR to catch issues. "review my changes", "review the diff", "check the fix before submitting", "does this look right".
Also in 4 projects that use this
testified-ossSkillincident-triage
Triage production incidents with severity assessment, root cause hypothesis, impact analysis, and escalation recommendations. Use when analyzing outages, errors, or production issues.
Also in 3 projects that use this
zbruhnkeSkillexplain-code
Explain how code works in detail. Use when trying to understand unfamiliar code, complex logic, or system architecture.
Also in 3 projects that use this
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 3 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- tirth8205/code-review-graph★ 33ksame name
- Arasz/ai-badger★ 3same name
- iadr-dev/colab★ 2same name
- imMamdouhaboammar/get-things-done★ 2same name
- johanolofsson72/Claude★ 2same name
- aprameyak/coding-skills★ 1same name
- exactbee/claude-code-workflow★ 1same name
- KMaruthi2002/universal-llm-skills★ 1same name
- rpraharaj/ai-engineer★ 1same name
- srclight/claude-code-plugin★ 1same name
3 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.
In this repository4 other files it gives its agents.
- code-reviewSkill
- debug-issueSkill
- session-startSkill
- using-basememSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Token Efficiency: Always prefer code_find and code_explore over whole-file reads.
“Common” is measured: kept by at least 6 in 10 of the 11 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
Codebase Exploration Protocol
Navigate codebase structure and AST symbols efficiently using indexed BaseMem queries.
Workflow
| Step | Tool | Input | Purpose |
| 1 | code_find | query="symbol", grep=True | Return matching filenames and line numbers (~0 tokens) |
| 2 | code_explore | query="symbol" | Discover callers, callees, and declaration signature |
| 3 | code_read | path, offset, limit (max 50 lines) | Read exact snippet containing the implementation |
Rules
- Token Efficiency: Always prefer
code_findandcode_exploreover whole-file reads. - Auto-Indexing: BaseMem auto-indexes on first use. If results are empty, call
code_init(repo_path="...").
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.