> **code_explorer** — chapter 17 of 24 in [google-gemini/gemini-cli](https://skillsdocs.com/google-gemini/gemini-cli).
>
> Book (all chapters, one file): https://skillsdocs.com/google-gemini/gemini-cli.md
> Machine manifest: https://skillsdocs.com/google-gemini/gemini-cli/.well-known/agent-skills/index.json
> Install the book: `npx skills add google-gemini/gemini-cli`
> Upstream: https://github.com/google-gemini/gemini-cli/blob/main/tools/caretaker-agent/cloudrun/triage-worker/.gemini/skills/code_explorer/SKILL.md @ `main`
> Raw bytes, no header: https://raw.githubusercontent.com/google-gemini/gemini-cli/main/tools/caretaker-agent/cloudrun/triage-worker/.gemini/skills/code_explorer/SKILL.md
> Base for relative paths: https://raw.githubusercontent.com/google-gemini/gemini-cli/main/tools/caretaker-agent/cloudrun/triage-worker/.gemini/skills/code_explorer/
> Licence: Apache-2.0 — https://spdx.org/licenses/Apache-2.0.html
>
> Content © its authors, served unmodified. Takedown: https://github.com/kyleledbetter/skillsdocs/issues/new?labels=takedown&title=Takedown+request

<!-- Verbatim upstream SKILL.md follows, YAML frontmatter included. -->

---
name: code_explorer
description: 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
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.

### Phase 3: Test Applicability & Pattern Check
1. **Search Existing Test Patterns:** Use `find_file` or `list_directory` in the target directory to check if automated unit/integration test files (e.g. `*.test.ts` or `*.test.tsx`) exist in that module.
2. **Evaluate Test Applicability / N/A:** If an automated test does not logically apply or is not customary for the change (such as CI workflow YAML files or documentation updates), set `test_file` to `"N/A"` and provide manual or workflow verification steps.

Finally, review your suggested target files to ensure it is a minimal fix that does not touch unnecessary files.

### Output Format:
Output a concise summary of the discovered file paths and technical context:
```json
{
  "primary_source_files": ["path/to/source.ts"],
  "related_files": [],
  "test_file": "path/to/test.test.ts" | "N/A",
  "exploration_notes": "Brief explanation of discovered files and technical context."
}
```