trace

Trace upstream and downstream module dependencies to generate a structured dependency map.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ImLp/claude-caide --skill trace-imlp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/ImLp/claude-caide/tree/main/.claude/skills/trace
Command: npx skills add https://github.com/ImLp/claude-caide --skill trace-imlp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reconstructs the complete dependency chain for a given module, exposing upstream and downstream relationships up to three levels deep to support impact analysis and planning.

Core Features & Use Cases

  • Upstream tracing: identify direct and transitive dependencies of a module.
  • Downstream tracing: discover all consumers and their relationships.
  • Structured output: produces a navigable map of module connectivity and an actionable summary.

Quick Start

Trace a module by name or path to generate its full dependency map.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I trace module dependencies for impact analysis?

You can trace module dependencies by applying the skill to a module by name or path. It reads wiki pages for imports and maps upstream and downstream relationships up to three levels deep.

What is upstream and downstream tracing in a module dependency graph?

Upstream tracing identifies direct and transitive dependencies of a module, while downstream tracing discovers all consumers. Together they expose complete architectural dependency chains.

Can I trace transitive dependencies beyond three levels deep?

No, module dependency tracing is limited to three levels deep. This depth limit ensures a consistent report when mapping architectural connections for impact analysis and planning.

How do I map architectural connections using module names or paths?

Map architectural connections by providing a module name or path. The skill reads wiki pages to extract imports and generates a navigable map showing module connectivity and relationships.

Does dependency tracing work by reading wiki pages for imports?

Yes, dependency tracing works by reading wiki pages for imports and dependencies. It uses this extracted information to reconstruct architectural connections and generate a structured dependency map.