Skip to content
Back to skills

Codebase Pattern Finder

ASecurity

Document existing code patterns

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
documentationdocumentation

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill codebase-pattern-finder --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Codebase Pattern Finder?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Codebase Pattern Finder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-codebase-pattern-finder/badge)](https://www.skillsdirectory.com/skills/david-li0406-codebase-pattern-finder)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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

1. Identify pattern types relevant to the user's query
2. Search using available tools
3. Extract relevant code sections with context
4. 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…