pattern-detection_skill

Overview

This skill identifies and documents recurring patterns in an existing codebase so new work aligns with project conventions. It focuses on naming, architecture, testing, imports/exports, and documentation to reduce friction when adding or reviewing code. Use it to preserve consistency and minimize unnecessary style debates.

How this skill works

I survey a small set of representative files (3–5) for the area you will change, extract repeating structures and naming rules, and check for explicit documentation or test conventions that confirm intent. I prioritize examples in the same module or feature, then project style guides, test files, and adjacent modules. Finally, I summarize the discovered patterns and provide concrete, actionable recommendations to apply in new code.

When to use it

• Before writing new code or scaffolding files
• During code review to validate adherence to conventions
• When onboarding to quickly learn project practices
• Before refactoring to avoid breaking established structure
• When adding tests to match the project test style

Best practices

• Follow existing patterns even when imperfect — consistency matters more than personal preference
• Document any intentional deviations and the reason for them
• Verify patterns in tests and sample files, not just inferred rules
• Prefer local examples (same module/feature) as the authoritative source
• Avoid introducing new patterns without a migration plan and team agreement

Example use cases

• Generate a new component that matches file naming, exports, and import ordering used by the project
• Review a pull request and flag naming or architectural inconsistencies
• Onboard a new engineer with a concise summary of repository conventions
• Add tests that follow the project’s test organization, naming, and setup patterns
• Refactor code while preserving dependency direction and layer boundaries