skill-reverse-engineeringlisted

# Reverse Engineering Skill ## Purpose Recover the mental model of a project from its codebase when documentation is outdated or missing. ## When to Use - Documentation-code mismatch detected - New team member onboarding - Post-"quick fix" cleanup ## Strategy: Automated Scan + Iterative Analysis ### Phase 1: Automated Directory Scan **Tool:** `scripts/scan_structure.py` **Usage:** ```bash python3 .agent/skills/skill-reverse-engineering/scripts/scan_structure.py . --depth 2 ``` **Goal:** - Get high-level overview of project structure. - Identify dominant languages and components. - Avoid context overflow by NOT reading all files. ### Phase 2: Local Analysis (Per-Directory) For each key component identified in Phase 1: 1. List files. 2. Sample 2-3 representative files (read content). 3. Generate **Local Summary**: - Purpose - Key Classes - Dependencies ### Phase 3: Global Synthesis Combine local summaries to update `docs/ARCHITECTURE.md`: - Update **Directory Structure** - Update **Component Map** - Identify **Architecture Drift** (Code != Docs) ## Output Artifacts ### 1. ARCHITECTURE.md Update Generate diffs for: - Directory Structure - Component Map - Data Flow ### 2. KNOWN_ISSUES.md Updates Identify: - `TODO`/`HACK` comments indicating tech debt. - Discrepancies between implementation and docs. **Filing format (thin index).** `docs/KNOWN_ISSUES.md` is a hand-maintained **thin index**, not a flat checklist — do **NOT** append `- [ ]` lines to it. The auth