anti-pattern-analysis

Detects design, architecture, database, testing, and security anti-patterns during code review with refactoring guidance.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/rubrical-works/idpf-praxis-skills --skill anti-pattern-analysis-rubrical-works
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: anti-pattern-analysis
Source: https://github.com/rubrical-works/idpf-praxis-skills/tree/main/Skills/anti-pattern-analysis
Command: npx skills add https://github.com/rubrical-works/idpf-praxis-skills --skill anti-pattern-analysis-rubrical-works

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code reviews often miss recurring structural problems like god objects, N+1 queries, flaky tests, and hardcoded secrets because reviewers lack a systematic detection framework. This Skill provides categorized anti-pattern checklists with severity levels and concrete refactoring steps so findings are consistent and actionable. ## Core Features & Use Cases - Systematic Detection Checklists: Covers design/OOP, code smells, architecture, database, testing, and security anti-patterns, each with severity ratings from Low to Critical. - Refactoring Guidance: Provides before/after code examples for common fixes such as extracting methods, guard clauses, eager loading for N+1 queries, and dependency inversion for circular dependencies. - Language-Specific Resources: Includes dedicated anti-pattern references for JavaScript, Python, Go, and Ruby. - Use Case: During a pull request review, apply the quick review checklist to flag a 1,200-line controller as a God Object (High severity), detect SQL string concatenation (Critical), and document both with suggested NFRs for a technical debt register. ## Quick Start Ask the AI to review a source file or module using the anti-pattern-analysis checklists and report each finding with its severity level and a suggested refactoring approach.

Frequently Asked Questions about anti-pattern-analysis

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

FAQPage Schema
How do I systematically detect anti-patterns during code review?▼

Apply categorized checklists covering design, code quality, database, testing, and security patterns. Each finding is documented with a severity level (Critical, High, Medium, Low) and a specific refactoring suggestion, such as extracting methods for long functions or eager loading for N+1 queries.

What are common database anti-patterns to check in code review?▼

Key database anti-patterns include N+1 queries, SELECT * usage, missing indexes, string-concatenated SQL, missing transactions, EAV schemas, and comma-separated values in columns. Each has detection steps and refactoring examples for ORMs like Django, SQLAlchemy, and Rails.

Which programming languages does this anti-pattern guidance cover?▼

The core checklists are language-agnostic and apply to JavaScript, TypeScript, Python, Java, Go, Rust, Ruby, and C#. Dedicated language-specific references exist for JavaScript, Python, Go, and Ruby covering issues like callback hell, goroutine leaks, and ignored error returns.

Can anti-pattern detection integrate with PRD or technical debt workflows?▼

Yes. Detected anti-patterns can be output in a structured table mapping each finding to a suggested non-functional requirement, such as NFR-SEC for security issues or NFR-PERF for query problems, supporting reverse-PRD extraction and technical debt documentation.

What severity levels are used for anti-pattern findings?▼

Four levels are used: Critical (security risk or data loss, must fix before merge), High (major technical debt, fix in same PR or sprint), Medium (code smell, create follow-up issue), and Low (minor improvement, optional).