code-explorer

Trace code features and map execution paths across repositories.

Updated Mar 14, 2019
One-click install
npx skills add https://github.com/twkevinzhang/opus-ed --skill code-explorer-twkevinzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-explorer
Source: https://github.com/twkevinzhang/opus-ed/tree/main/.agent/skills/code-explorer
Command: npx skills add https://github.com/twkevinzhang/opus-ed --skill code-explorer-twkevinzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes codebases to trace feature implementations, capture execution paths, and map integration points for safe, informed changes.

Core Features & Use Cases

  • Trace feature implementations: map call graphs and file-level dependencies
  • Identify integration points: find interfaces, adapters, and boundaries between modules
  • Architecture-aware analysis: detect patterns like Repository/Service/Controller, gateways, and data flows
  • Use Case: Reason about a proposed change by tracing impacted files and related components

Quick Start

Provide a repository path or task title to begin a comprehensive codebase analysis.

Frequently Asked Questions about code-explorer

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

FAQPage Schema
How do I trace feature implementations and execution paths across a codebase?

To trace execution paths, you map call graphs and file-level dependencies from entry points to outputs. This captures data transformations and cross-cutting concerns to document integration points for safe changes.

What is the best way to identify integration points and boundaries between modules?

Identifying integration points involves finding interfaces, adapters, and boundaries between modules. Architecture-aware analysis detects patterns like Repository/Service/Controller and gateways to clarify data flows.

Can I analyze codebases of varying sizes for architecture patterns?

Yes, architecture-aware analysis applies to codebases of varying sizes. It detects patterns like Repository/Service/Controller and traces explicit call chains to provide precise file-level references.

How do I map call graphs and file-level dependencies for a proposed change?

Map call graphs and file-level dependencies by tracing impacted files and related components. Reasoning about a proposed change requires capturing execution paths and cross-cutting concerns to ensure safe modifications.

Does code exploration work with data transformations and cross-cutting concerns?

Code exploration works by tracing data transformations and cross-cutting concerns across a repository. It maps execution paths from entry points to outputs, providing precise file-level references and documented integration points.