semantic-code-search

Search code systematically to identify references and assess impact.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/msageha/maestro_v2 --skill semantic-code-search-msageha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semantic-code-search
Source: https://github.com/msageha/maestro_v2/tree/main/templates/skills/worker/semantic-code-search
Command: npx skills add https://github.com/msageha/maestro_v2 --skill semantic-code-search-msageha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers systematically search for code, understand its impact, and identify relevant areas for refactoring or testing by providing a structured approach to code analysis.

Core Features & Use Cases

  • Systematic Code Search: Employs a 5-step analysis flow (Identify, Pattern Search, Reference Analysis, Classify, Verify) for comprehensive code discovery.
  • Impact Analysis: Helps determine the ripple effects of code changes by analyzing direct and indirect references.
  • Test Case Identification: Assists in pinpointing code sections that require testing based on their usage and impact.
  • Use Case: When refactoring a core UserService function, use this Skill to identify all places it's called, understand which other services depend on it, and classify the risk level of the change.

Quick Start

Use the semantic-code-search skill to find all usages of the 'calculate_total' function and analyze its impact.

Frequently Asked Questions about semantic-code-search

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

FAQPage Schema
How do I perform impact analysis before refactoring a core function?

Impact analysis for refactoring requires a systematic search to identify all direct and indirect references, classify the risk level of code changes, and verify the results across multiple packages.

What is the best way to map code dependencies across multiple packages?

Dependency mapping across packages is best achieved through a multi-stage search methodology that identifies patterns, analyzes references comprehensively, and classifies the potential impact of changes.

How do I identify test cases for a function I need to refactor?

Test case identification during refactoring involves searching for all code usages, analyzing how the target function is referenced by other services, and pinpointing areas that require testing based on their impact.

Can I use standard search tools like Grep and Glob for comprehensive code discovery?

Yes, systematic code discovery utilizes tools like Grep and Glob alongside an Explore SubAgent to facilitate comprehensive reference analysis and classification of code impact across the repository.

What is code impact classification and when do I need it?

Code impact classification is the process of determining the ripple effects of code changes by analyzing references, and it is needed when undertaking software engineering tasks involving dependency mapping or refactoring.