explore-codebase
Skill3 starsChanged 31 days agoMITView on GitHub
Use when arriving at an unfamiliar codebase, or an unfamiliar region of a known one, and the question is "what is here and how is it arranged" rather than "where is this specific thing". Trigger phrases: "help me understand this repo", "what does this project do", "where does X live", "walk me through the architecture", "I'm new to this codebase", "what are the main modules". Not for tracing one symptom to its cause — that is `debug-issue`; not for judging a diff — that is `review-changes`. Reach for this one when orienting, and switch to those once you know where to look.
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
- ashvin-to/BaseMemtheir own version, first seen Oct 19, 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 incident-triage, explain-code 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.
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
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
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
- iadr-dev/colab★ 2same name
- imMamdouhaboammar/get-things-done★ 2same name
- johanolofsson72/Claude★ 2same name
- aprameyak/coding-skills★ 1same name
- ashvin-to/BaseMem★ 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 repository52 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .ai-badger/AGENTS.mdAGENTS.md
- .ai-badger/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .ai-badger/copilot-instructions.mdCopilot instructions
- .github/copilot-instructions.mdCopilot instructions
- ai-raccoon-memorySkill
- archifySkill
- artifact-verificationSkill
- auto-wmSkill
- browser-usageSkill
- call-behavioristSkill
- code-review-checklistSkill
- code-review-evidenceSkill
- commit-reminderSkill
- complete-project-scope-code-reviewSkill
- create-task-specSkill
- debug-issueSkill
- den-refreshSkill
- design-gate-auditSkill
- design-testsSkill
- differential-feature-refactorSkill
- documentation-drift-auditSkill
- documentationSkill
- evidence-first-researchSkill
- feed-badgerSkill
- git-workSkill
- humanizerSkill
- maintain-agent-instructionsSkill
- mcp-indexSkill
- multi-agent-communicationSkill
- multi-lane-report-assemblySkill
- owner-gate-reviewSkill
- pre-push-gate-debuggingSkill
- prompt-markersSkill
- qaSkill
- quick-taskSkill
- refactor-safelySkill
- research-record-auditSkill
- review-changesSkill
- review-gate-diff-verificationSkill
- review-testsSkill
- scripts-tooling-refactorSkill
- semantica-knowledge-graphSkill
- send-messageSkill
- spec-driven-refactoringSkill
- status-reportSkill
- task-decompositionSkill
- taskSkill
- test-economySkill
- welcome-ai-badgerSkill
- worktree-agent-isolationSkill
The file
Files
This is the generic copy. If this project has been scaffolded, prefer the unprefixed
explore-codebaseskill: it is.ai-badger/skills/explore-codebase/SKILL.md, and it has this project's extensions and anyproject-local.mdmerged in. This copy has neither.The full procedure is in
SKILL.full.mdbeside this file, unchanged — read it if the project has no.ai-badger/, or runwelcome-ai-badgerto scaffold one.
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.

