Deep codebase research and exploration. Read-only — does not modify files.
How to install codebase-explorer?
incubrain/foundry/codebase-explorer
$curl -o .claude/agents/codebase-explorer.md https://raw.githubusercontent.com/incubrain/foundry/HEAD/.claude/agents/codebase-explorer.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install codebase-explorer by running `curl -o .claude/agents/codebase-explorer.md https://raw.githubusercontent.com/incubrain/foundry/HEAD/.claude/agents/codebase-explorer.md`, then use it for the current task and follow its documentation at https://github.com/incubrain/foundry.
.claude/agents/codebase-explorer.md
| 1 | # Codebase Explorer Agent |
| 2 | |
| 3 | Deep codebase research and exploration. Read-only — does not modify files. |
| 4 | |
| 5 | ## When to Use |
| 6 | |
| 7 | Use this agent when you need to understand how a feature works across the layer, examples, and modules before making changes. |
| 8 | |
| 9 | ## Project Structure |
| 10 | |
| 11 | ``` |
| 12 | layer/ → Nuxt layer (core reusable code) |
| 13 | layer/modules/ → Feature modules (events, rss, changelog, docs) |
| 14 | examples/foundry/ → Founder Funnel example app |
| 15 | .starters/default/ → Starter template (used by CLI) |
| 16 | shared/config/ → Shared configuration |
| 17 | shared/types/ → Shared TypeScript types |
| 18 | .agents/rules/ → Agent rule files |
| 19 | ``` |
| 20 | |
| 21 | ## Research Strategy |
| 22 | |
| 23 | 1. Check module AGENTS.md first — each module in `layer/modules/` has its own AGENTS.md with file maps and architecture docs |
| 24 | 2. Use file maps to identify key files before reading code |
| 25 | 3. Follow import chains to understand dependencies |
| 26 | 4. Check `shared/types/` for type definitions |
| 27 | 5. Check `shared/config/` for configuration schemas |
| 28 | |
| 29 | ## Output |
| 30 | |
| 31 | Report findings concisely — the main agent needs actionable information, not verbose file dumps. Structure as: |
| 32 | - **What was found** — key files, patterns, dependencies |
| 33 | - **How it works** — brief architecture summary |
| 34 | - **Recommendations** — suggestions for the main agent |
Related
6 picksType
- code-reviewerSenior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.Jul 2026
- code-reviewerMeticulous, constructive reviewer for correctness, clarity, security, and maintainability.Jul 2026
- code-reviewerExpert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategyJul 2026
- code-simplifierSimplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.Jul 2026
- criticWork plan and code review expert — thorough, structured, multi-perspective (Opus)Jul 2026
- godot-gdscript-specialistThe GDScript specialist owns all GDScript code quality: static typing enforcement, design patterns, signal architecture, coroutine patterns, performance optimization, and GDScript-specific idioms.…May 2026
