Menü
Patterns and techniques for analyzing brownfield codebases. Use when onboarding to unfamiliar code, preparing for refactoring, conducting architecture reviews, or identifying technical debt.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Generic BAML patterns for type-safe LLM prompting. Covers schema design, DTO generation, client wrappers, and cross-language codegen. Framework-agnostic.
Browser automation for documentation discovery. Use when curl fails on JS-rendered sites, when detecting available browser tools, or when configuring browser-based documentation collection.
C4 architectural modeling for documenting software architecture. Use when creating architecture diagrams, planning new systems, communicating with stakeholders, or conducting architecture reviews.
Debug and analyze web applications using Chrome DevTools MCP. Use for console log inspection, network request monitoring, performance analysis, and debugging authenticated sessions. For basic browser automation (screenshots, form filling), use browser-discovery skill instead.
Detect new imports in modified files and auto-install missing dependencies. Works with npm, uv, pip, cargo, go mod, and other package managers. Triggers after code implementation to keep manifests in sync.
Navigate hierarchical ai-docs indexes to find documentation. Check local docs FIRST for speed and curated context before web searching. Covers Claude Code, BAML, MCP, and other tracked libraries.
| name | codebase-analysis |
| description | Patterns and techniques for analyzing brownfield codebases. Use when onboarding to unfamiliar code, preparing for refactoring, conducting architecture reviews, or identifying technical debt. |
Systematically explore and understand existing codebases, including entry point discovery, dependency tracing, pattern detection, and technical debt identification.
| Variable | Default | Description |
|---|---|---|
| ANALYSIS_DEPTH | standard | quick (5min), standard (30min), deep (1hr+) |
| OUTPUT_FORMAT | markdown | markdown, json, c4 |
| INCLUDE_DEBT | true | Include technical debt assessment |
| INCLUDE_DIAGRAMS | true | Generate C4 diagrams |
MANDATORY - Follow the Workflow steps below in order. Do not skip steps.
If you're about to:
STOP -> Read the appropriate cookbook file -> Follow the workflow -> Then proceed
cookbook/entry-point-discovery.md)cookbook/entry-point-discovery.mdcookbook/dependency-tracing.mdcookbook/pattern-detection.mdcookbook/debt-identification.md| Stack | Look For |
|---|---|
| Node.js | package.json main/bin, index.js, server.js |
| TypeScript | tsconfig.json, src/index.ts |
| Python | __main__.py, app.py, wsgi.py |
| Go | main.go, cmd/*/main.go |
| React | src/index.tsx, pages/_app.tsx |
See reference/framework-patterns.md for complete list.
| Pattern | Directory Signs |
|---|---|
| MVC | models/, views/, controllers/ |
| Layered | presentation/, business/, data/ |
| Hexagonal | domain/, ports/, adapters/ |
| Microservices | services/*/, packages/*/ |
# Codebase Analysis: [Project Name]
## Overview
- **Size**: X files, Y lines
- **Primary Language**: TypeScript
- **Framework**: Next.js
- **Architecture**: [Pattern]
## Entry Points
1. `src/pages/_app.tsx` - Application root
2. `src/api/` - API routes
## Key Dependencies
- [External deps list]
## Architecture Diagram
[C4 diagram if INCLUDE_DIAGRAMS]
## Technical Debt (if INCLUDE_DEBT)
| Issue | Severity | Location |
|-------|----------|----------|
| ... | High | ... |