Code Smells (Detection + Guidance)

Use this skill when users ask to assess code for smells, refactoring opportunities, maintainability issues, or general code quality.

Operating rules

• Diagnose first: identify and classify smells before proposing edits.
• Use canonical smell names from this skill's catalog exactly.
• Anchor findings to concrete evidence (file/function/line or behavior).
• Pair smell findings with this quality checklist when applicable:
• Input validation at boundaries
• No code injection
• Error handling
• Configuration and constants
• Architecture and design
• Frontend safety
• Type hints (Python)
• Documentation hygiene
• Do not refactor automatically; only propose changes unless implementation is explicitly requested.
• Prioritize findings by impact and risk.