# Bloat Review Lens

Review the provided code for **size and complexity bloat**.

## What to Look For

### File-Level
- Files over 300 lines (warning) or 500 lines (critical)
- Files with multiple unrelated responsibilities (SRP violations)
- God objects or god modules that do too much

### Function-Level
- Functions over 50 lines
- Functions with more than 5 parameters
- Functions that could be split into smaller, named steps

### Complexity
- Cyclomatic complexity hotspots (many branches/loops)
- Deeply nested logic (3+ levels of indentation)
- Long method chains that obscure intent

## Output Format

For each finding:
```
[BLOAT] <severity:HIGH|MED|LOW> <file:line>
Issue: <what's bloated>
Why: <why this is a problem>
Suggest: <concrete action - split into X, extract Y, etc.>
```

## Guidelines

- Be specific about line counts and locations
- Prioritize by impact (high-traffic code > rarely-used)
- Don't flag intentionally comprehensive files (test fixtures, generated code)
- Focus on actionable splits, not just complaints
