# Locate Relevant Code

Finds the source, UI and test files tied to a bug report or feature request.

- Repository: https://github.com/google-gemini/gemini-cli (108651 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add google-gemini/gemini-cli --skill code_explorer -g -a claude-code -y`
Codex: `npx skills add google-gemini/gemini-cli --skill code_explorer -g -a codex -y`
Cursor: `npx skills add google-gemini/gemini-cli --skill code_explorer -g -a cursor -y`
Gemini CLI: `npx skills add google-gemini/gemini-cli --skill code_explorer -g -a gemini-cli -y`

## Description

Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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
1. **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.
2. **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
1. **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.
2. **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.
3. **Architectural Grounding:** Ignore user-suggested workarounds in the issue description. Always investigate the underlying source code to derive a clean fix.

The rest: https://github.com/google-gemini/gemini-cli/blob/HEAD/tools/caretaker-agent/cloudrun/triage-worker/.gemini/skills/code_explorer/SKILL.md