skills.rest
ybbms777
ybbms777COMMUNITY
Explore all skills by this author →
GitHub

pattern-recognition-specialist

Analyze codebases for design patterns, anti-patterns, and duplication.

1|Updated Apr 4, 2026
Search Tags:#code quality#code analysis#anti-patterns#design patterns#architectural review#naming conventions#code duplication
One-click install
npx skills add https://github.com/ybbms777/compound-engineering --skill pattern-recognition-specialist-ybbms777
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pattern-recognition-specialist
Source: https://github.com/ybbms777/compound-engineering/tree/main/skills/agent-pattern-recognition-specialist
Command: npx skills add https://github.com/ybbms777/compound-engineering --skill pattern-recognition-specialist-ybbms777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually reviewing large codebases for design patterns, anti-patterns, naming inconsistencies, code duplication, and architectural boundary violations is time-consuming, inconsistent, and prone to oversight, leading to accumulated technical debt and degraded code quality over time.

Core Features & Use Cases

  • Design Pattern Detection: Identifies common design patterns (Factory, Singleton, Observer, Strategy, etc.) across the codebase and evaluates their implementation against established best practices.
  • Anti-Pattern & Code Smell Scanning: Flags technical debt indicators including TODO/FIXME/HACK comments, God objects, circular dependencies, and inappropriate class coupling with severity assessments.
  • Naming & Duplication Analysis: Evaluates consistency of naming conventions across variables, functions, classes, and files, and detects duplicated code blocks to recommend refactoring into shared utilities.
  • Architectural Boundary Review: Checks for layer violations, cross-module dependencies, and abstraction bypasses that break intended architectural principles.
  • Use Case: A development team preparing for a major refactor can use this skill to quickly map all existing design patterns, identify high-impact anti-patterns, and get a prioritized list of refactoring tasks to reduce technical debt efficiently.

Quick Start

Use the pattern-recognition-specialist skill to analyze your project's codebase for design patterns, anti-patterns, naming inconsistencies, and code duplication, then generate a structured report with prioritized refactoring recommendations.

Frequently Asked Questions about pattern-recognition-specialist

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

FAQPage Schema
How do I detect anti-patterns and code smells in my codebase?▼

Code analysis scans your codebase to flag technical debt indicators like God objects, circular dependencies, and inappropriate class coupling with severity assessments. It evaluates your code against established best practices to highlight areas needing refactoring and reduce accumulated debt.

What is the best way to check for architectural boundary violations before a merge?▼

Checking for architectural boundary violations involves reviewing your codebase for layer violations, cross-module dependencies, and abstraction bypasses. This ensures new code aligns with intended architectural principles and prevents structural degradation during pre-merge consistency checks.

How do I identify duplicated code blocks and naming inconsistencies across multiple programming languages?▼

Identifying code duplication and naming inconsistencies requires analyzing variables, functions, classes, and files across multiple programming languages. The analysis evaluates naming convention consistency and detects duplicated blocks to recommend refactoring into shared utilities.

Can I evaluate existing design patterns against best practices during a technical debt assessment?▼

Yes, you can evaluate existing design patterns during a technical debt assessment by analyzing your codebase to identify common patterns like Factory, Singleton, Observer, and Strategy. The review checks their implementation against established best practices to ensure structural quality.

Does this code analysis approach work for prioritizing refactoring tasks in large codebases?▼

Yes, this approach works for large codebases by delivering structured reports with prioritized, actionable refactoring recommendations. It aligns suggestions with existing project conventions and architectural constraints to help teams reduce technical debt efficiently.

Related Skills

Explore More Software Engineering Skills→
Fr-e-dFr-e-d
157

architecture-extract

Analyze project directory structures to generate architectural summaries.

Community
Basic
CristoVenturesCristoVentures
2

pattern-recognition-specialist

Identify design patterns, anti-patterns, and code quality issues across codebases.

Official
Advanced
nanorepublicananorepublica
61

Testing Unit Tests

Standardize unit-test coding practices across Claude Code projects.

Community
Basic
quan0715quan0715
31

qjudge-quality-gates-owner

Enforce naming, import boundary, and Carbon style quality gates in CI.

Community
Intermediate