pattern-recognition-specialist

Identify design patterns, anti-patterns, and duplicated code in multi-language repositories.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill pattern-recognition-specialist-jikig-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pattern-recognition-specialist
Source: https://github.com/jikig-ai/soleur/tree/main/.openhands/skills/pattern-recognition-specialist
Command: npx skills add https://github.com/jikig-ai/soleur --skill pattern-recognition-specialist-jikig-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams and reviewers rapidly find design patterns, anti-patterns, naming inconsistencies, and duplicated code so that architectural issues and technical debt can be identified and prioritized for refactoring.

Core Features & Use Cases

  • Design Pattern Detection: Locate common patterns (Factory, Singleton, Observer, Strategy, etc.), report their locations, and assess implementation quality against best practices.
  • Anti-Pattern and Code Smell Identification: Find TODO/FIXME/HACK markers, god classes, circular dependencies, inappropriate intimacy, and feature envy with severity assessments.
  • Naming and Consistency Analysis: Evaluate naming conventions across variables, functions, classes, files, and configuration constants and surface deviations with concrete examples.
  • Duplication Detection & Architectural Review: Run token-based duplication detection (e.g., jscpd-style) with configurable thresholds and analyze cross-layer boundary violations to flag separation-of-concern breaches.
  • Use Case: During a pre-release architecture review, use this Skill to produce a prioritized report of pattern usage, code smells, naming issues, and duplication hotspots to guide refactoring and code ownership.

Quick Start

Ask the agent to scan the repository for design patterns, TODO/FIXME markers, naming inconsistencies, and duplicated code and return a structured report with locations, severity, and remediation suggestions.

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 design patterns and anti-patterns in a multi-language codebase?

To detect design patterns and anti-patterns in a multi-language codebase, perform grep and AST-based searches to locate implementations like Factory or Singleton, and identify code smells such as god classes and circular dependencies with severity assessments.

What is the best way to scan for TODO and FIXME markers during an architecture review?

The best way to scan for TODO and FIXME markers during an architecture review is to run automated TODO/FIXME/HACK scanning across the repository, which surfaces technical debt hotspots and flags areas requiring immediate remediation.

How do I check naming conventions across variables and functions for consistency?

To check naming conventions across variables and functions for consistency, run a naming consistency analysis that evaluates identifiers against established conventions and surfaces deviations with concrete examples.

Can I use token-based duplication detection with configurable thresholds for refactoring prioritization?

Yes, you can use token-based duplication detection with configurable thresholds to identify duplicated code blocks, allowing you to prioritize refactoring tasks based on the severity and location of the duplication hotspots.

Does static analysis help identify cross-layer boundary violations and separation of concerns breaches?

Yes, static analysis helps identify cross-layer boundary violations and separation of concerns breaches by analyzing architectural dependencies, flagging inappropriate intimacy, and reporting feature envy during code review.