code-smells
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.
More from bout3fiddy/agents
coding
Core engineering skill for implementation, bug fixes, refactors, and technical reviews with mandatory smell guardrails and targeted domain reference routing.
61planning
Planning workflows for clarifying ambiguous build requests, running spec/work-package delivery, and managing Linear lifecycle transitions.
31skill-creator
Create, update, or install skills (including planning/specs and edits to skills/*) using our repo workflow (uv + skills-ref validation, lean SKILL.md, references/ for detail, and sync via bin/sync.sh).
26housekeeping
Organize and modernize AGENTS.md and CLAUDE.md context systems. Use when the user works on structuring, migrating, or curating agent instruction files and repo context architecture.
25design
Frontend design curation skill for UI critique, motion storyboarding, and DialKit tuning. Use when the user asks for interface feedback, animation sequencing, or interactive design-control setup.
19agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
6