Locate definitions, references, and occurrences of symbols in source code.
npx skills add https://github.com/MichaelYagi/mcp_a2a --skill code-search
Please help me install this Agent Skill. Skill: code_search Source: https://github.com/MichaelYagi/mcp_a2a/tree/main/servers/code_review/skills/code_search Command: npx skills add https://github.com/MichaelYagi/mcp_a2a --skill code-search
The Code Search Skill helps developers quickly locate definitions, references, and occurrences across a codebase, reducing the time spent manual code triage.
Use the code_search skill to locate the definition of the function "process_user" in the repository.
High-intent search queries and answers about installing and using this skill.
To find all references to a function across multiple files, use code search to locate definitions, call sites, and symbol occurrences across your project. It traces data flow by fetching all usages during debugging tasks.
The best way to locate class definitions during a code audit is using pattern-based queries to search source code. This approach identifies symbols and definitions across languages without manual triage.
Yes, you can use textual search to navigate code relationships in large repositories. Pattern-based queries identify symbols, definitions, and usages, allowing you to map code structure across multi-file projects.
Code search works across different programming languages for debugging by applying textual search and pattern-based queries to source code. It identifies symbols, definitions, and occurrences regardless of language.
To trace data flow when debugging a function call, search the codebase to fetch all call sites and definitions for that function. This maps how data moves through the system.
winsorllcSearches GitHub repositories for code via the GitHub API.
Snowflake-LabsA concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略
hbvg234Trace error symptoms to execution paths and call graphs using GitNexus queries.
raybirdAnalyze source code changes to identify dependencies and potential breaking changes.
