bloat-detector

# Bloat Detector Systematically detect and eliminate codebase bloat through progressive analysis tiers. ## Bloat Categories | Category | Examples | |----------|----------| | **Code** | Dead code, God classes, Lava flow, duplication | | **AI-Generated** | Tab-completion bloat, vibe coding, hallucinated deps | | **Documentation** | Redundancy, verbosity, stale content, slop | | **Dependencies** | Unused imports, dependency bloat, phantom packages | | **Git History** | Stale files, low-churn code, massive single commits | ## Quick Start ### Tier 1: Quick Scan (2-5 min, no tools) ```bash /bloat-scan ``` Detects: Large files, stale code, old TODOs, commented blocks, basic duplication ### Tier 2: Targeted Analysis (10-20 min, optional tools) ```bash /bloat-scan --level 2 --focus code # or docs, deps ``` Adds: Static analysis (Vulture/Knip), git churn hotspots, doc similarity ### Tier 3: Deep Audit (30-60 min, full tooling) ```bash /bloat-scan --level 3 --report audit.md ``` Adds: Cross-file redundancy, dependency graphs, readability metrics ## When To Use | Do | Don't | |----|-------| | Context usage > 30% | Active feature development | | Quarterly maintenance | Time-sensitive bugs | | Pre-release cleanup | Codebase < 1000 lines | | Before major refactoring | Tools unavailable (Tier 2/3) | ## When NOT To Use - Active feature development - Time-sensitive bugs - Codebase < 1000 lines ## Confidence Levels | Level | Confidence | Action | |-------|------------|--------| |...