code-smell
Catálogo de 94 code smells em TypeScript/JavaScript organizados em 12 categorias (Bloaters, Couplers, Dispensables, Object-Orientation Abusers, Naming & Readability, entre outras), cada um com exemplo de má prática e a refatoração correspondente, baseado no artigo de Gilvam Mourão. Acione como passada obrigatória de fechamento em TODA tarefa que cria, edita, refatora, escreve ou organiza código TypeScript/JavaScript — em projeto novo ou existente, não só em code review — ao nomear um problema de design (método longo, muitos parâmetros, condicional aninhado, duplicação, acoplamento excessivo) e justificar a refatoração via SOLID/Clean Code, antes de reportar a mudança como concluída ou abrir PR. Rode por último, depois da skill de implementação, junto de code-standards-en e typescript-sonarqube. Não use para detectar bugs funcionais (use testes e type-checker), medir performance objetivamente (use profiling/benchmarks), nem para aplicar regras de estilo automatizadas (use ESLint/Prettier/Biome).
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.
