code-explore

Traces execution paths and maps architecture to produce structured code investigation reports.

189|25|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/sd0xdev/sd0x-harness --skill code-explore-sd0xdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-explore
Source: https://github.com/sd0xdev/sd0x-harness/tree/main/skills/code-explore
Command: npx skills add https://github.com/sd0xdev/sd0x-harness --skill code-explore-sd0xdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Understanding an unfamiliar codebase or diagnosing why a feature behaves unexpectedly requires hours of manual file reading. This Skill automates that investigation by systematically locating entry points, tracing call chains, and producing a structured analysis report. ## Core Features & Use Cases - Four-Phase Investigation Workflow: Locates entry points with Grep/Glob, traces execution paths through Controller/Service/Provider layers, analyzes core logic and data flow, then outputs a formatted report. - Search Pattern Library: Ships a reference guide of ready-made Grep and Glob patterns for finding API endpoints, services, providers, models, and configuration files. - Structured Report Output: Delivers an architecture overview, key files table, execution flow, data flow description, and actionable findings. - Use Case: Ask why an API intermittently returns empty results, and the Skill traces the data retrieval path, identifies fallback and timeout handling, and lists probable causes with recommendations. ## Quick Start Ask the agent to investigate how a specific feature works in this repository and produce an architecture and execution-flow report.

Frequently Asked Questions about code-explore

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

FAQPage Schema
How do I trace an execution path through a codebase?▼

Start by grepping for route or method keywords to find the entry point, then read each file to follow calls through Controller, Service, and Provider layers. The Skill maps the full call chain and outputs it as a numbered execution flow.

How to understand what a feature does in an unfamiliar repository?▼

Grep for feature-related keywords to locate relevant files, identify the entry points, then trace dependencies layer by layer. The result is a report with an architecture overview, key files table, and data flow description.

What is the difference between code-explore and code-investigate?▼

code-explore is a fast, single-perspective investigation using only Claude's tools, suited for quick research. code-investigate adds Codex cross-validation for dual confirmation, making it slower but better for important decisions.

When should I not use code exploration for a task?▼

Avoid it when you need dual-perspective confirmation, git history analysis, system-level verification, or formal code review. Those scenarios map to code-investigate, git-investigate, feature-verify, and codex-review-fast respectively.

Can code exploration help diagnose why an API returns empty results?▼

Yes. It greps for the relevant data and cache keywords, traces the retrieval path, and examines fallback logic and timeout handling. The final report lists probable causes with recommendations.