pattern-detection

Analyze repository structure to detect naming, architecture, and testing patterns.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/I2olanD/dotfiles --skill pattern-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pattern-detection
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/pattern-detection
Command: npx skills add https://github.com/I2olanD/dotfiles --skill pattern-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency. Use when generating code, reviewing changes, or understanding established practices. Ensures new code aligns with project conventions.

Core Features & Use Cases

  • Pattern discovery: detect naming conventions, architectural layers, and test organization across a repository.
  • Consistency enforcement: guide refactoring and new code to follow project conventions.
  • Use Case: Before adding a feature, run this skill to ensure naming and architecture choices align with the project style.

Quick Start

Provide a repository path or URL to analyze. The skill will scan for naming conventions, architectural patterns, and testing structures and return a pattern report.

Frequently Asked Questions about pattern-detection

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

FAQPage Schema
How do I identify existing codebase patterns for naming conventions and architecture?

To identify codebase patterns, provide a repository path or URL for analysis. The skill scans the repository structure to detect established naming conventions, architectural layers, and testing practices, returning an actionable pattern report.

What is the best way to maintain code consistency when adding new features to a project?

Maintaining code consistency involves scanning the repository to extract existing architectural layers and naming conventions before generating new code. This ensures new features align with project standards and established practices.

Can I analyze a remote repository URL to detect testing patterns and architectural layers?

Yes, you can analyze a remote repository URL. The skill accepts a repository path or URL, scanning it to surface testing structures, architectural layers, and naming conventions to guide development.

Does this pattern detection approach work for onboarding developers to established project conventions?

Yes, pattern detection works for onboarding by analyzing repository structure to surface naming conventions and testing practices. It outputs actionable guidance helping new developers understand and align with established project standards.

When should I avoid using automated codebase pattern detection for refactoring?

Avoid automated codebase pattern detection when a repository lacks sufficient established code for accurate convention extraction, or when immediate structural changes are needed before baseline patterns can be analyzed and documented.