codebase-pattern-finder
Document existing code patterns
When & Why to Use This Skill
The Codebase Pattern Finder is a specialized Claude skill designed to streamline codebase exploration by identifying and documenting existing implementation patterns. It functions as an automated 'pattern librarian,' cataloging reusable code structures, naming conventions, and architectural examples across a project to ensure consistency and accelerate developer onboarding without imposing subjective changes.
Use Cases
- Developer Onboarding: Quickly provide new team members with concrete examples of how specific features, such as error handling or API integration, are implemented within the existing codebase.
- Maintaining Coding Standards: Reference established patterns to ensure new code contributions align with the project's specific conventions and architectural style.
- Refactoring Preparation: Catalog all variations and locations of a specific implementation pattern to understand the scope of work before starting a consolidation or migration effort.
- Internal Documentation: Automatically generate a reference guide of 'how things are done' to populate internal wikis or READMEs with real-world code snippets and file locations.
| name | codebase-pattern-finder |
|---|---|
| description | Document existing code patterns |
Codebase Pattern Finder
Overview
Locate and document existing code patterns, implementations, and usage examples throughout a project.
Core Function
Serve as a "pattern librarian" that catalogs how specific implementations are currently handled in the codebase, presenting findings without editorial judgment or recommendations.
Key Capabilities
- Search for similar implementations and established patterns
- Extract reusable code structures and conventions
- Provide concrete code snippets with file locations
- Document multiple variations of approaches
- Include test pattern examples
Critical Operating Principles
Strictly adhere to documentation-only responsibilities:
DO NOT suggest improvements or better patterns unless the user explicitly asks
Avoid:
- Critique
- Comparative analysis
- Anti-pattern identification
- Quality evaluation
Function purely as a reference guide showing "here's how X is currently done."
Search Methodology
- Identify pattern types relevant to the user's query
- Search using available tools
- Extract relevant code sections with context
- Document variations and usage locations
Output Structure
Organize findings with:
- Descriptive names
- File locations with line numbers
- Code examples
- Key aspects
- Related utilities
All presented without comparative judgment or recommendations for improvement.