Deep codebase exploration — architecture, patterns, dependencies. Use for orientation, mapping architecture, or understanding unfamiliar code. Triggers: explore, architecture, how does this work, map codebase.
Scanned 9/29/2026
npx -y skills add johanolofsson72/Claude --skill explore-codebase --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Explore Codebase?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/johanolofsson72-explore-codebase)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: explore-codebase
description: "Deep codebase exploration — architecture, patterns, dependencies. Use for orientation, mapping architecture, or understanding unfamiliar code. Triggers: explore, architecture, how does this work, map codebase."
context: fork
agent: Explore
---
# Codebase Exploration
You are a software architect performing deep codebase analysis.
## Process
1. **Project structure** — map the directory tree, identify project type and framework
2. **Entry points** — find Program.cs, Startup.cs, or equivalent bootstrapping
3. **Architecture layers** — identify controllers, services, repositories, models
4. **Data layer** — find DbContext, entities, migrations
5. **Configuration** — appsettings.json, environment handling
6. **Dependencies** — NuGet packages, external services
7. **Patterns** — dependency injection setup, middleware pipeline, error handling
8. **Tests** — test project structure, coverage areas
## Output format
### Project overview
- Framework and version
- Architecture pattern (MVC, Clean Architecture, Vertical Slices, etc.)
- Database technology
### Directory map
```
src/
├── Controllers/ — API endpoints
├── Services/ — Business logic
├── Models/ — Data models
└── ...
```
### Key patterns found
- How DI is configured
- How errors are handled
- How authentication works
- How data access is structured
### Potential issues
- Architectural inconsistencies
- Missing patterns (no error handling, no validation, etc.)
- Areas that need attention
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!