Pattern Search

Group code pattern implementations using semantic search and git history.

11|3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill pattern-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Pattern Search
Source: https://github.com/artk0de/TeaRAGs-MCP/tree/main/.claude-plugin/tea-rags/skills/pattern-search
Command: npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill pattern-search

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of agents blindly copying code by providing context-aware search that prioritizes stable, battle-tested implementations over hotspots or technical debt.

Core Features & Use Cases

  • History-Aware Discovery: Enriches search results with authorship, churn, and bug-fix rate data.
  • Strategic Search: Uses a decision tree to select the optimal search tool based on intent, such as collecting examples or identifying antipatterns.
  • Use Case: When refactoring a legacy module, use this skill to find all existing implementations of a specific design pattern across the entire repository, filtered by stability and ownership metrics.

Quick Start

Use the pattern search skill to collect all implementations of the authentication middleware pattern across the codebase.

Frequently Asked Questions about Pattern Search

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

FAQPage Schema
How do I find all implementations of a specific code pattern across a large repository?

To find code pattern implementations across a repository, this skill uses semantic search integrated with git history to group matching code and distinguish stable logic from high-churn technical debt.

What is the best way to identify technical debt hotspots using git history?

Identifying technical debt hotspots is achieved by enriching code search results with git metadata, measuring authorship, file churn, and bug-fix rates to isolate unstable code regions.

How does semantic code search help with refactoring legacy modules?

Semantic code search aids refactoring by locating existing design pattern implementations across complex codebases, prioritizing battle-tested stable code over high-churn areas to prevent copying bad patterns.

Can I filter code search results by code stability and ownership metrics?

Yes, you can filter code search results by stability and ownership metrics, as the skill evaluates git-based historical data like authorship and bug-fix rates to rank reliable code patterns.

When should I use history-aware code search instead of standard text search?

Use history-aware code search when analyzing complex codebases for refactoring, requiring context-aware discovery to avoid blindly copying unstable implementations or technical debt hotspots.