analyzing-codebases

What problem does it solve?

Manually exploring and understanding a new or existing codebase requires hours of tedious work, constant context switching, and repeated questions to team members, especially when joining a new project, preparing for major architectural changes, or onboarding new engineers or AI sessions.

Core Features & Use Cases

• Layered Deep-Dive Analysis: Automatically maps project structure, dependencies, core data models, end-to-end business flows, and coding conventions without manual input.
• Flexible Analysis Modes: Choose between quick (~5 minute survey), thorough (~15-20 minute full analysis), or exhaustive (~30+ minute deep scan) modes to match your available time and depth needs.
• Structured Reporting: Generates a comprehensive markdown report covering architecture overview, dependency graphs, technical debt markers, complexity hotspots, and key flow traces, with git commit tracking to compare analysis results over time.
• Use Case: When joining a new engineering team, run this skill to get a complete overview of the project's architecture, key business flows, and existing technical debt in minutes instead of spending days manually exploring the codebase.

Quick Start

Use the analyzing-codebases skill to generate a full codebase analysis report for the current project, including architecture overview, dependency maps, and health assessment.