skills.rest
rameshkumarchouhanr
rameshkumarchouhanrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code_explorer

Locates source files, related components, and test files for reported issues.

Updated Aug 26, 2026
Search Tags:#stack trace#bug report#monorepo#code exploration#issue triage#file discovery#test detection
One-click install
npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill code-explorer-rameshkumarchouhanr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code_explorer
Source: https://github.com/rameshkumarchouhanr/gemni-cli/tree/main/tools/caretaker-agent/cloudrun/triage-worker/.gemini/skills/code_explorer
Command: npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill code-explorer-rameshkumarchouhanr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When triaging bug reports or feature requests, finding the right files to change in a large multi-package repository is time-consuming and error-prone. This Skill systematically explores the codebase to identify verified file paths and technical context for a reported issue. ## Core Features & Use Cases - Root-Level Exploration: Builds a high-level understanding of the repository structure (e.g., packages/cli, packages/core) before narrowing down, so cross-package fixes are not missed. - Directed Traversal: Traces stack traces, logs, and imports across package boundaries to capture all affected caller and consumer files. - 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 pointing into packages/core, the Skill traces the error to its source definition, finds related UI components in packages/cli, and outputs a JSON summary of primary source files, related files, and the applicable test file. ## 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 related to 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 trace data flow across package boundaries to capture all affected files.

How to trace errors across multiple packages in a monorepo?▼

Begin at the exact file referenced in the stack trace, then follow imports and data flow across package boundaries such as packages/cli and packages/core. Shared utilities and caller files in sibling packages must be included in the traversal.

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

Set the test_file field 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 fixes from an issue description?▼

No. User-suggested workarounds in issue descriptions should be ignored. Always investigate the underlying source code directly to derive a clean, architecturally grounded fix.

What output format does the code exploration produce?▼

The exploration produces a JSON object with primary_source_files, related_files, test_file (a path or "N/A"), and exploration_notes summarizing the discovered files and technical context.

Related Skills

Explore More Software Engineering Skills→
JuniYadiJuniYadi

issue-parser

Parse GitHub issue titles and bodies to extract errors, file paths, and function names.

Community
Intermediate
DataDogDataDog
648

run-tests

Identify changed files and run affected test suites via scripts/run-tests.

Official
Advanced
sumilee-pcusumilee-pcu

bug-triage

Parse bug reports to classify severity and priority for sprint planning.

Community
Advanced
opensage-agentopensage-agent
113

get-caller

Identify direct and indirect callers of functions using Neo4j callgraph data.

Official
Intermediate