ai-code-smells
Detects AI-generated code smells — over-engineering, YAGNI abstractions, defensive/self-referential comments, gold-plated DI/IoC seams, excessive design patterns, over-documentation of trivial APIs, tutorial verbosity in production, test over-specification, empty boilerplate, misplaced genericity, over-eager immutability, type-restating error messages, and bleeding-edge syntax with no domain reason. Use when the user asks to scan for AI code smells, review code, audit codebase quality, or check if code is up to standards. Also applies proactively when writing or editing code. Produces clean, minimal code without introducing these smells.
Works with
This skill's source license couldn't be confirmed as safe to mirror here, so it isn't inlined. View the full skill directly on its source repository.
View on GitHubMore Refactoring skills
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
analyze-project
lllllllama/rigorpilot-skills
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.
request-refactor-plan
mattpocock/skills
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
