code_explorer

Explores repositories to locate source files, related components, and test files for reported issues.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/bkrsna/gemini-cli --skill code-explorer-bkrsna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code_explorer
Source: https://github.com/bkrsna/gemini-cli/tree/main/tools/caretaker-agent/cloudrun/triage-worker/.gemini/skills/code_explorer
Command: npx skills add https://github.com/bkrsna/gemini-cli --skill code-explorer-bkrsna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When triaging bug reports or feature requests, developers waste time manually hunting through large codebases to find the files that actually need to change. This Skill automates that exploration, producing a verified list of primary source files, related files, and applicable test files. ## Core Features & Use Cases - Hypothesis-Driven Exploration: Forms an initial hypothesis from the issue title and body, then explores the full repository structure rather than a single subfolder. - Cross-Package Tracing: Follows imports, stack traces, and data flow across package boundaries (e.g., packages/cli and packages/core) to capture all affected callers and consumers. - Test Applicability Check: Searches for existing test patterns (e.g., *.test.ts) and marks test_file as "N/A" with manual verification steps when automated tests do not apply. - Use Case: Given a GitHub issue with a stack trace, the Skill traces the error to its source definition, identifies sibling files needing coordinated changes, and outputs a structured JSON summary for the next triage step. ## Quick Start Explore the repository for the attached bug report and return the primary source files, related files, and applicable test file as JSON.

Frequently Asked Questions about code_explorer

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

FAQPage Schema
How do I find the source files responsible for a bug report?

Start from any stack trace, log, or file reference in the issue body and follow imports down to the original definitions. Form a hypothesis about the issue domain first, then explore candidate directories across the whole repository rather than one subfolder.

How to trace bugs across multiple packages in a monorepo?

Trace data flow across package boundaries, such as between packages/cli and packages/core, and through shared utilities to capture all affected caller and consumer files. A complete fix often requires coordinated changes in sibling packages.

What should I do when no automated test applies to a change?

Set the test file to "N/A" when automated tests do not logically apply, such as for CI workflow YAML files or documentation updates. Provide manual or workflow verification steps instead.

Should I follow user-suggested workarounds in an issue description?

No. Ignore user-suggested workarounds and investigate the underlying source code directly to derive a clean, architecturally grounded fix that touches the minimal set of files.

What output does the code exploration produce?

It produces a JSON object listing primary source files, related files, the applicable test file or "N/A", and brief exploration notes explaining the discovered technical context.