explore

Search codebases using glob, grep, LSP, AST, and git history.

16|1|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/bahayonghang/my-claude-code-settings --skill explore-bahayonghang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore
Source: https://github.com/bahayonghang/my-claude-code-settings/tree/main/skills/explore
Command: npx skills add https://github.com/bahayonghang/my-claude-code-settings --skill explore-bahayonghang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides fast, precise codebase search capabilities to locate code, files, and patterns within the current project, enabling developers to quickly answer questions about where something is located, how code is organized, and how components relate.

Core Features & Use Cases

  • Locate a specific function, class, or symbol anywhere in the repository.
  • Search across files and modules to map code structure and dependencies.
  • Understand module organization and trace call relationships (definitions, references, and usage).

Quick Start

Ask the Explore skill to find the definition of a function or to list all references to a symbol in the current project.

Frequently Asked Questions about explore

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

FAQPage Schema
How do I find the definition of a function in a large codebase?

To find a function definition in a codebase, you can use multi-angle search techniques like glob, grep, LSP, and AST parsing. This approach pinpoints exact file paths and context across large repositories without needing specialized installations.

What is the best way to locate all references to a symbol in a project?

Locating all references to a symbol involves tracing call relationships and usage across files and modules. Using LSP and AST searches maps code structure and dependencies, returning precise locations and contextual data for the queried symbol.

Can I search for code patterns and files without installing specialized tools?

Yes, you can search for code patterns and files without specialized installations. The search leverages built-in techniques like glob, grep, and git history to output precise file paths and context directly within the current project environment.

How does searching git history help locate code and understand module organization?

Searching git history helps locate code by revealing past changes and component relationships within the repository. It traces structural evolution and dependencies, enabling developers to understand how modules are organized and interact over time.

Are there limitations when using grep and glob to map code structure in large repositories?

While grep and glob quickly locate files and patterns in large repositories, they may lack semantic context compared to LSP or AST searches. Relying solely on text matching can sometimes miss complex call relationships and structural dependencies.