Identify and categorize code antipatterns with symptoms, examples, and fixes.
npx skills add https://github.com/smileynet/code-spice --skill code-antipatterns
Please help me install this Agent Skill. Skill: code-antipatterns Source: https://github.com/smileynet/code-spice/tree/main/skills/code-antipatterns Command: npx skills add https://github.com/smileynet/code-spice --skill code-antipatterns
This Skill helps developers identify and rectify common code smells and antipatterns that degrade software quality, making code fragile, surprising, or hard to maintain.
Use the code-antipatterns skill to find and fix silent failures in the codebase.
High-intent search queries and answers about installing and using this skill.
To identify code smells during a code review, evaluate functions against antipattern categories like surprise, misuse, complexity, and premature optimization. This process isolates fragile code structures, providing severity classifications and refactoring examples to improve maintainability.
The best way to refactor boolean blindness is to replace ambiguous boolean parameters with readable enums or configuration objects. This refactoring strategy clarifies function intent, categorizes the issue as a misuse antipattern, and provides specific examples to fix the surprising code.
To fix silent failures in your codebase, consult the antipattern catalog to identify the specific misuse or surprise category causing the issue. You receive detailed symptoms, context-dependent evaluation tables, and targeted refactoring guidance to rectify the degraded software quality.
You need to evaluate software design for premature optimization when auditing plans or reviewing code that adds unnecessary complexity. Using antipattern categorization, you can assess the severity of the optimization and determine if refactoring is required to restore maintainability.
Common categories of code antipatterns include surprise, misuse, complexity, and premature optimization. Identifying these specific categories helps developers recognize symptoms, apply context-dependent evaluation tables, and implement targeted fixes to improve overall code quality.
BerryKuipersRecord code quality metrics before refactoring into a timestamped JSON baseline.
bostonaholicReview code for SOLID design violations and suggest refactoring steps.
nicolanoviellReview code changes for bugs, style issues, and best practices.
tartinerlabsAudit TypeScript/JavaScript codebases for dead code, deep nesting, and design smells.
