explore-codebase

Map a codebase's structure, conventions, and architecture into codebase-knowledge.md.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/son-nguyen-301/hydra-claude --skill explore-codebase-son-nguyen-301
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore-codebase
Source: https://github.com/son-nguyen-301/hydra-claude/tree/main/skills/explore-codebase
Command: npx skills add https://github.com/son-nguyen-301/hydra-claude --skill explore-codebase-son-nguyen-301

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill maps a codebase's structure, conventions, and architecture into a centralized codebase-knowledge artifact that can be consumed by future sessions.

Core Features & Use Cases

  • Codebase mapping: discovers modules, directory structure, and conventions to speed onboarding.
  • Memory integration: persists findings into the workspace memory for later retrieval during planning and development tasks.
  • Use Case: A new team member can ask the agent to "understand the project structure" and receive a structured codebase map.

Quick Start

Start the skill to generate a codebase map and ingest it into the project memory.

Frequently Asked Questions about explore-codebase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map codebase architecture for new project onboarding?

Mapping codebase architecture for onboarding is done by analyzing directory structure, modules, and conventions, then storing the findings in a centralized knowledge file for future sessions to ingest.

Can I memorize codebase structure into workspace memory for future sessions?

Yes, you can memorize codebase structure by generating a codebase-knowledge.md file saved in workspace memory, allowing future sessions to automatically load project context during development.

What's the best way to capture codebase conventions and module structure for a team?

Capturing codebase conventions and module structure is best handled by generating a centralized codebase map artifact that documents architecture and conventions, then persists it into workspace memory for team retrieval.

Does generating a codebase map require any external dependencies or components?

Generating a codebase map requires no external dependencies or components, as the skill runs standalone to analyze project files and output a knowledge markdown file directly into workspace memory.

How to do an architectural review using a codebase knowledge file?

An architectural review using a codebase knowledge file involves triggering the skill to map existing modules and conventions, then consulting the generated knowledge artifact to assess structure and identify architectural patterns.

When should I not use automated codebase mapping for project documentation?

Automated codebase mapping may not suit projects with heavily obfuscated code or dynamic runtime architectures that cannot be statically analyzed from directory structures and file conventions alone.