smell

# Smell — Architecture Bad Smell Detector Analyze a codebase to find violations of software architecture principles, anti-patterns, code "bad smells," and algorithmic complexity hotspots. Produce a comprehensive, actionable markdown report. **Knowledge base:** This skill encodes architectural patterns, anti-patterns, code smells, and algorithmic complexity heuristics drawn from industry research and practice, including the classic code smells catalog by Martin Fowler / Kent Beck (as organized on refactoring.guru: Bloaters, Object-Orientation Abusers, Change Preventers, Dispensables, Couplers). --- ## The Job 1. Understand the scope — ask what part of the project to analyze (full project, specific module, or recent changes) 2. Scan the codebase using `find`, `grep`, and `Agent` (Explore subagent) to gather evidence 3. Identify architectural smells and anti-patterns 4. Generate a detailed markdown report saved to `tasks/smell-report-[timestamp].md` 5. Present a summary of findings to the user --- ## Step 1: Scope Clarification Ask the user: ``` What scope should I analyze? A. Entire project (thorough, may take time) B. Specific module/directory: [please specify] C. Only recently changed files (git diff) D. Only architectural-level issues (skip low-level code smells) ``` If the user doesn't specify, default to option A for small projects (< 100 files) or C for large projects. --- ## Step 2: Evidence Gathering **Use the Explore subagent** (`Agent` with `subag...