analyzing-patterns
Automatically activated when user asks to "find patterns in...", "identify repeated code...", "analyze the architecture...", "what design patterns are used...", or needs to understand code organization, recurring structures, or architectural decisions
npx skills add majiayu000/claude-skill-registry --skill analyzing-patterns --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Analyzing Patterns You are an expert in recognizing software design patterns, architectural patterns, and code organization strategies. This skill provides systematic pattern analysis to identify recurring structures, conventions, and design decisions in codebases. ## Your Capabilities 1. **Design Pattern Recognition**: Identify Gang of Four and modern design patterns 2. **Architectural Pattern Analysis**: Recognize system-level patterns and structures 3. **Code Pattern Detection**: Find repeated code structures and conventions 4. **Convention Extraction**: Document naming, organization, and style patterns 5. **Anti-Pattern Identification**: Spot problematic patterns and suggest improvements ## When to Use This Skill Claude should automatically invoke this skill when: - User asks "what patterns are used in this code?" - Questions about "find repeated/duplicated code" - Requests to "analyze the architecture" - Asking about "design patterns in this codebase" - Understanding code organization strategies - Identifying naming conventions - Recognizing structural similarities - Refactoring opportunities - Code review focusing on patterns ## Pattern Analysis Methodology ### Phase 1: Pat
- Your Capabilities
- When to Use This Skill
- Pattern Analysis Methodology
- Phase 1: Pattern Discovery
- Phase 2: Pattern Analysis
- Phase 3: Synthesis & Reporting
- Pattern Categories
- Design Patterns (Gang of Four)
- Architectural Patterns
- Code-Level Patterns
- Analysis Strategies
- Finding Design Patterns
- Finding Architectural Patterns
- Finding Code Patterns
Factory Pattern
grep -r "factory\|create.*Function\|build.*Function" --include="*.ts"
Singleton Pattern
grep -r "getInstance\|static.*instance" --include="*.js"
Observer Pattern
grep -r "subscribe\|addEventListener\|on\(" --include="*.ts"
Strategy Pattern
grep -r "interface.*Strategy\|class.*Strategy" --include="*.ts"
Decorator Pattern
grep -r "@.*decorator\|class.*Decorator" --include="*.ts"What does the analyzing-patterns skill do?
Automatically activated when user asks to "find patterns in...", "identify repeated code...", "analyze the architecture...", "what design patterns are used...", or needs to understand code organization, recurring structures, or architectural decisions
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill analyzing-patterns --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.