anti-patterns

Catalog common SDLC anti-patterns for code and architecture reviews.

75|13|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/avelikiy/great_cto --skill anti-patterns-avelikiy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anti-patterns
Source: https://github.com/avelikiy/great_cto/tree/main/skills/anti-patterns
Command: npx skills add https://github.com/avelikiy/great_cto --skill anti-patterns-avelikiy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps avoid common Software Development Life Cycle (SDLC) pitfalls by cataloging anti-patterns and providing guidance for their resolution.

Core Features & Use Cases

  • Catalogue of Anti-Patterns: Reference a comprehensive list of SDLC anti-patterns.
  • Use Case: When reviewing code, architecture, or post-mortems, use the Skill to identify and reject anti-patterns that can lead to system failures.

Quick Start

Use the anti-patterns skill to identify anti-patterns in the code review of 'module_X'.

Frequently Asked Questions about anti-patterns

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

FAQPage Schema
What are common SDLC anti-patterns to check for during a code review?

Common SDLC anti-patterns to check during a code review include architectural flaws and coding practices that reduce system robustness and maintainability. This Skill provides a structured catalogue to help identify and reject these recurring pitfalls.

How do I use anti-pattern references for post-mortem analysis?

You use anti-pattern references for post-mortem analysis by matching documented system failures against a catalogue of known SDLC pitfalls. This helps identify the root architectural or coding missteps that caused the failure and prevents their recurrence.

Can I apply an SDLC anti-patterns catalogue to architecture reviews?

Yes, you can apply an SDLC anti-patterns catalogue to architecture reviews. It provides a structured reference to identify and reject architectural decisions that undermine system robustness, ensuring better long-term maintainability.

Do I need prior knowledge of common software anti-patterns to use this reference?

Yes, you need awareness of common anti-patterns and an understanding of their implications on system robustness to use this reference effectively. It serves as a structured guide for teams to identify and reject pitfalls during reviews.

What is the best way to prevent common Software Development Life Cycle failures?

The best way to prevent common Software Development Life Cycle failures is to reference a curated catalogue of anti-patterns during code reviews and architecture planning. This helps teams identify and reject pitfalls that lead to system failures.

Why does referencing anti-patterns improve system maintainability?

Referencing anti-patterns improves system maintainability by exposing recurring architectural and coding pitfalls before they cause system failures. It provides structured guidance to help development teams avoid decisions that degrade long-term robustness.