code-antipatterns

Identify and categorize code antipatterns with symptoms, examples, and fixes.

Updated Feb 17, 2026

Search Tags:#code quality #code review #refactoring #software design #maintainability #antipatterns

Ready to run

npx skills add https://github.com/smileynet/code-spice --skill code-antipatterns

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers identify and rectify common code smells and antipatterns that degrade software quality, making code fragile, surprising, or hard to maintain.

Core Features & Use Cases

Antipattern Catalog: Provides a comprehensive list of antipatterns categorized by type (Surprise, Misuse, Complexity, Premature).
Code Review Aid: Assists in code reviews by offering checklists and decision tables to evaluate code quality.
Refactoring Guidance: Offers strategies and examples for fixing identified antipatterns.
Use Case: During a code review, a developer encounters a function with many boolean parameters. They can consult this Skill to identify "Boolean Blindness" as an antipattern and learn how to refactor it into a more readable enum or configuration object.

Quick Start

Use the code-antipatterns skill to find and fix silent failures in the codebase.

Frequently Asked Questions about code-antipatterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify code smells and antipatterns during a code review?▼

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.

What is the best way to refactor code with boolean blindness?▼

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.

How do I fix silent failures in my codebase?▼

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.

When do I need to evaluate software design for premature optimization?▼

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.

What are the common categories of code antipatterns?▼

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.