sd-explore

Trace code execution paths from entry points to data storage.

2|2|Updated Jul 10, 2024
One-click install
npx skills add https://github.com/kslhunter/simplysm --skill sd-explore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sd-explore
Source: https://github.com/kslhunter/simplysm/tree/main/.claude/skills/sd-explore
Command: npx skills add https://github.com/kslhunter/simplysm --skill sd-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deeply analyze a codebase by tracing entry points, call flows, and data transformations to produce a clear, actionable map of architecture and dependencies, without modifying the source code.

Core Features & Use Cases

  • End-to-end trace: Identify entry points, core implementation files, and how data flows between layers.
  • Architecture mapping: Document layer boundaries, design patterns, and interfaces between components.
  • Use Case: When investigating a feature in a large monorepo, trace from UI or API entry to storage to understand dependencies and potential impact.

Quick Start

Provide a complete trace of a target codebase path from entry points to data storage, generating a dependency map and architecture diagram.

Frequently Asked Questions about sd-explore

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

FAQPage Schema
How do I trace code execution paths from entry points to data storage?

To trace code execution paths, identify entry points and follow call flows and data transformations to produce an architecture map. This reveals how a feature is implemented across layers without modifying source code.

What is the best way to analyze dependencies in a large monorepo?

Analyzing dependencies in a large monorepo involves mapping feature implementation from UI or API entry to storage. This generates a dependency list with file paths and line references to understand potential impact.

Can I map architecture and document layer boundaries without changing the source code?

You can map architecture and document layer boundaries without changing source code by tracing call flows and interfaces. This produces an architecture diagram and dependency map detailing design patterns across components.

Does codebase tracing work across diverse programming languages and frameworks?

Codebase tracing works across diverse languages, frameworks, and architectures. It enables feature-level mapping and dependency analysis by generating call graphs that track data flow end-to-end regardless of stack.

How to generate a call graph for a specific feature implementation?

To generate a call graph for a specific feature implementation, trace execution paths from entry points through core implementation files. This yields a visual architecture map and dependency list with precise file paths and line references.