codebase-analysislisted

# Codebase Analysis Skill Systematically explore and understand existing codebases, including entry point discovery, dependency tracing, pattern detection, and technical debt identification. ## Variables | 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 | ## Instructions **MANDATORY** - Follow the Workflow steps below in order. Do not skip steps. - Start with entry points, not random files - Trace dependencies before analyzing patterns - Document findings as you go ## Red Flags - STOP and Reconsider If you're about to: - Analyze random files without finding entry points first - Make architectural claims without tracing dependencies - Skip pattern detection before identifying anti-patterns - Report technical debt without severity classification **STOP** -> Read the appropriate cookbook file -> Follow the workflow -> Then proceed ## Workflow 1. [ ] Quick Assessment: Project size, structure, config files 2. [ ] **CHECKPOINT**: Identify entry points (read `cookbook/entry-point-discovery.md`) 3. [ ] Trace dependencies from entry points 4. [ ] Detect architectural patterns 5. [ ] **CHECKPOINT**: Verify pattern detection before anti-pattern search 6. [ ] Identify anti-patterns and technical debt 7. [ ] Doc