Locate Relevant Code
Finds the source, UI and test files tied to a bug report or feature request.
Install
npx skills add google-gemini/gemini-cli --skill code_explorer -g -a claude-code -y- Repository
- google-gemini/gemini-cli109k
- Category
- Engineering
- Updated
- 4d ago
- License
- Apache-2.0
- Context cost
- Lightabout 618 tokens
- Runs scripts
- No, instructions only
What it does
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
Code Explorer Instructions
Explore the repository to find verified, existing file paths and technical context related to the reported issue.
Phase 1: Root Exploration & Related Area Discovery
- Understand Overall Codebase Structure: Before focusing on a single file, gain a high-level understanding of the repository structure (e.g.
packages/cli,packages/core). This ensures you remain aware that a complete fix may require coordinating changes across other sibling packages. Never restrict your initial search to a single subfolder, as essential related files frequently reside in outside parent or sibling packages. - Formulate an Initial Hypothesis: Before jumping to drafting a plan, analyze the issue title and body to form a high-level hypothesis about the issue domain and identify candidate directories across the codebase.
Phase 2: Directed Code Exploration & Traversal
- Error Tracing: If the issue body contains a stack trace, log, or file reference, start at that exact file. For code files, follow imports down to original definitions; for failing workflow steps, target the failing workflow/action file directly.
- Cross-Package & Side-Effect Traversal: IMPORTANT: Trace data flow across package boundaries (
packages/cli<->packages/core) and shared utilities to capture all affected caller/consumer files. - Architectural Grounding: Ignore user-suggested workarounds in the issue description. Always investigate the underlying source code to derive a clean fix.
