find-similar
Find similar or analogous code patterns elsewhere in a codebase. Use when answering "Do we do something similar elsewhere?" or "What existing patterns match this?" Returns factual findings about similar code - locations, similarity type, and confidence.
Best use case
find-similar is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Find similar or analogous code patterns elsewhere in a codebase. Use when answering "Do we do something similar elsewhere?" or "What existing patterns match this?" Returns factual findings about similar code - locations, similarity type, and confidence.
Teams using find-similar should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/find-similar/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How find-similar Compares
| Feature / Agent | find-similar | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Find similar or analogous code patterns elsewhere in a codebase. Use when answering "Do we do something similar elsewhere?" or "What existing patterns match this?" Returns factual findings about similar code - locations, similarity type, and confidence.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Find Similar Patterns A conceptual framework for systematically finding similar or analogous code patterns in a codebase. **This skill is factual, not prescriptive.** It helps find and report what exists. It does not recommend whether to use, ignore, or modify findings. **Tools available:** Grep, Glob, Read, Bash (git commands) --- ## Similarity Types "Similar" can mean different things. Identify which type matters before searching. | Type | What It Means | Example | |------|---------------|---------| | **Lexical** | Same names, keywords, identifiers | "Where else do we call `formatDate`?" | | **Structural** | Same code shape, different names | "Where else do we have retry logic?" | | **Analogous** | Same role in a different domain | "What's the equivalent handler in another domain?" | | **Conceptual** | Same purpose, potentially different approach | "How do we handle validation elsewhere?" | --- ## Search Strategy ### Level 1: Direct Search Search for the thing itself or obvious variations. - Exact terms, function names, type names - Known synonyms or alternate spellings - Import/export statements **Stop if:** Found clear matches. ### Level 2: Sibling/Peer Discovery Find files that serve the same role. - Files in the same directory - Files with the same naming pattern (e.g., `*.handler.ts`, `use*.ts`) - Files in parallel directories (e.g., `domains/users/` → `domains/projects/`) **Stop if:** Found peers that reveal the pattern. ### Level 3: Reference Tracing Follow the dependency graph. - Where is X defined? - What imports/uses X? - What does X import/use? **Stop if:** Found the relevant connected files. ### Level 4: Conceptual Expansion Broaden the search with related concepts. - Synonyms and related terms - Different implementations of the same idea - Cross-domain analogues **Stop if:** Found conceptually similar code, or exhausted reasonable search terms. --- ## Confidence Levels | Confidence | Criteria | |------------|----------| | **HIGH** | Exact or near-exact match; clearly the same pattern | | **MEDIUM** | Similar structure or purpose; some differences | | **LOW** | Conceptually related; different approach or partial match | **Factors that affect confidence:** - Same directory/domain → higher - Same naming conventions → higher - Same imports/dependencies → higher - Different structure or approach → lower --- ## What to Capture (adapt to your context) Useful information to track for each finding: - **Location** — file path and line range - **Similarity type** — which of the four types applies - **Confidence** — how close is the match - **Why similar** — brief explanation of the relationship For negative results, note what was searched so coverage can be verified. --- ## Tips - **Start narrow, expand as needed** — Don't search the entire codebase if a directory search suffices - **Use file organization as signal** — Sibling files often reveal local conventions - **Git history can help** — Files that change together are often related - **Report what you searched** — Helps verify coverage and enables follow-up
Related Skills
weather-safety-guardrails
Keep activity suggestions safe and respect local conditions
structured-itinerary-responses
Present time-aware itineraries with clear actions and citations
write-docs
Write or update documentation for the Inkeep docs site (agents-docs package). Use when: creating new docs, modifying existing docs, introducing features that need documentation, touching MDX files in agents-docs/content/. Triggers on: docs, documentation, MDX, agents-docs, write docs, update docs, add page, new tutorial, API reference, integration guide.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
slack-manifest
Guide for modifying the Slack app manifest — adding/removing bot scopes, event subscriptions, slash commands, shortcuts, or OAuth config. Ensures single-source-of-truth via slack-app-manifest.json. Triggers on: slack scope, bot scope, slack manifest, slack permission, add slack scope, remove slack scope, slack event subscription, slash command, slack OAuth, slack-app-manifest.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
route-handler-authoring
Conventions for writing Hono route handlers that forward validated bodies to DAL functions, and CRUD test requirements for round-trip field persistence. Triggers on: creating new routes, modifying handlers, adding CRUD tests, route handler patterns, field-picking, spread pattern, DAL forwarding, check:route-handler-patterns, CI check failure.
product-surface-areas
Consolidated dependency graph of Inkeep customer-facing surface areas (UIs, CLIs, SDKs, APIs, protocols, config formats). Example use: as a prd-time (planning/brainstorming phase) or post-change checklist to understand the full scope of side-effects or what making one change to the product means for the rest. Use whenever you need to understand the "ripple" out effects of any change.
pr-review-appsec-vendored
Stack-specific application security checklist for this repo's frameworks: better-auth, SpiceDB/AuthZed, and Next.js RSC. Extends the generalizable pr-review-appsec agent with patterns that require framework-specific knowledge to detect. Loaded by pr-review-appsec.
next-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods