codebase-search

Search and navigate large codebases using semantic search, grep patterns, and glob file discovery.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/juanjaragavi/utilities-manager --skill codebase-search-juanjaragavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-search
Source: https://github.com/juanjaragavi/utilities-manager/tree/main/.agents/skills/codebase-search
Command: npx skills add https://github.com/juanjaragavi/utilities-manager --skill codebase-search-juanjaragavi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Locating specific functions, tracing call chains, and understanding unfamiliar codebases is slow and error-prone when done manually, especially across large repositories with many files and languages. ## Core Features & Use Cases - Multi-Strategy Search: Combines semantic search for conceptual questions, grep for exact patterns, and glob for file discovery across Python, JavaScript, TypeScript, Go, Java, and C++. - Structured Workflows: Provides step-by-step recipes for finding definitions, tracing data flow, mapping callsites, and running impact analysis before refactoring. - Use Case: Before renaming a shared function, use this Skill to find its definition, enumerate every callsite with grep, locate related tests via glob, and read each usage to plan a safe change. ## Quick Start Use the codebase-search skill to find where user authentication is implemented and trace all of its callsites.

Frequently Asked Questions about codebase-search

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

FAQPage Schema
How do I find where a function is defined in a large codebase?▼

Use grep with language-specific patterns such as "def function_name" for Python or "function functionName" for JavaScript, filtered by file type. Combine with glob to narrow the search to relevant directories first.

How to find all callsites of a function before refactoring?▼

First locate the definition with grep, then search for all imports of its module, and finally grep for the function name followed by an opening parenthesis. Read each matching file to confirm the usage context.

When should I use semantic search instead of grep?▼

Use semantic search for conceptual questions like "how is authentication handled" when you do not know exact identifiers. Use grep when you know precise names, error messages, or string patterns to match.

Why does my grep search return no results in a codebase?▼

Check spelling and case sensitivity, broaden the scope by removing directory targets, and verify the files are not excluded by .gitignore. Trying alternative search terms or semantic search often resolves misses.

Can git history help understand legacy code?▼

Yes, git blame shows who changed each line, git log -S finds when a function was introduced, and git log --grep locates commits mentioning a feature. These complement static search with change context.