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)
/bloat-scan
Detects: Large files, stale code, old TODOs, commented blocks, basic duplication
Tier 2: Targeted Analysis (10-20 min, optional tools)
/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)
/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) |
Confidence Levels
| Level |
Confidence |
Action |
| HIGH |
90-100% |
Safe to remove |
| MEDIUM |
70-89% |
Review first |
| LOW |
50-69% |
Investigate |
Prioritization
Priority = (Token_Savings × 0.4) + (Maintenance × 0.3) + (Confidence × 0.2) + (Ease × 0.1)
Module Architecture
Tier 1 (always available):
@module:quick-scan - Heuristics, no tools@module:git-history-analysis - Staleness, churn, vibe coding signatures
Tier 2 (optional tools):
@module:code-bloat-patterns - Anti-patterns (God class, Lava flow)@module:ai-generated-bloat - AI-specific patterns (Tab bloat, hallucinations)@module:documentation-bloat - Redundancy, readability, slop detection@module:static-analysis-integration - Vulture, Knip
Shared:
@module:remediation-types - DELETE, REFACTOR, CONSOLIDATE, ARCHIVE
Auto-Exclusions
Always excludes: .venv, __pycache__, .git, node_modules, dist, build, vendor
Also respects: .gitignore, .bloat-ignore
Safety
- Never auto-delete - all changes require approval
- Dry-run support -
--dry-run for previews
- Backup branches - created before bulk changes
Related
bloat-auditor agent - Executes scansunbloat-remediator agent - Safe remediationcontext-optimization skill - MECW principles
1---2name: bloat-detector-43description: Detect codebase bloat through progressive analysis: dead code, duplication, complexity, documentation bloat. Triggers: bloat detection, dead code, code cleanup, duplication, technical debt, unused code Use when: context usage high, quarterly maintenance, pre-release cleanup, before refactoring DO NOT use when: active feature development, time-sensitive bugs, codebase < 1000 lines4---56# Bloat Detector78Systematically detect and eliminate codebase bloat through progressive analysis tiers.910## Bloat Categories1112| Category | Examples |13|----------|----------|14| **Code** | Dead code, God classes, Lava flow, duplication |15| **AI-Generated** | Tab-completion bloat, vibe coding, hallucinated deps |16| **Documentation** | Redundancy, verbosity, stale content, slop |17| **Dependencies** | Unused imports, dependency bloat, phantom packages |18| **Git History** | Stale files, low-churn code, massive single commits |1920## Quick Start2122### Tier 1: Quick Scan (2-5 min, no tools)23```bash24/bloat-scan25```26Detects: Large files, stale code, old TODOs, commented blocks, basic duplication2728### Tier 2: Targeted Analysis (10-20 min, optional tools)29```bash30/bloat-scan --level 2 --focus code # or docs, deps31```32Adds: Static analysis (Vulture/Knip), git churn hotspots, doc similarity3334### Tier 3: Deep Audit (30-60 min, full tooling)35```bash36/bloat-scan --level 3 --report audit.md37```38Adds: Cross-file redundancy, dependency graphs, readability metrics3940## When to Use4142| Do | Don't |43|----|-------|44| Context usage > 30% | Active feature development |45| Quarterly maintenance | Time-sensitive bugs |46| Pre-release cleanup | Codebase < 1000 lines |47| Before major refactoring | Tools unavailable (Tier 2/3) |4849## Confidence Levels5051| Level | Confidence | Action |52|-------|------------|--------|53| HIGH | 90-100% | Safe to remove |54| MEDIUM | 70-89% | Review first |55| LOW | 50-69% | Investigate |5657## Prioritization5859```60Priority = (Token_Savings × 0.4) + (Maintenance × 0.3) + (Confidence × 0.2) + (Ease × 0.1)61```6263## Module Architecture6465**Tier 1** (always available):66- `@module:quick-scan` - Heuristics, no tools67- `@module:git-history-analysis` - Staleness, churn, vibe coding signatures6869**Tier 2** (optional tools):70- `@module:code-bloat-patterns` - Anti-patterns (God class, Lava flow)71- `@module:ai-generated-bloat` - AI-specific patterns (Tab bloat, hallucinations)72- `@module:documentation-bloat` - Redundancy, readability, slop detection73- `@module:static-analysis-integration` - Vulture, Knip7475**Shared**:76- `@module:remediation-types` - DELETE, REFACTOR, CONSOLIDATE, ARCHIVE7778## Auto-Exclusions7980Always excludes: `.venv`, `__pycache__`, `.git`, `node_modules`, `dist`, `build`, `vendor`8182Also respects: `.gitignore`, `.bloat-ignore`8384## Safety8586- **Never auto-delete** - all changes require approval87- **Dry-run support** - `--dry-run` for previews88- **Backup branches** - created before bulk changes8990## Related9192- `bloat-auditor` agent - Executes scans93- `unbloat-remediator` agent - Safe remediation94- `context-optimization` skill - MECW principles
majiayu000