explain

Explain code architecture, data flows, and dependencies for onboarding.

13|3|Updated Mar 27, 2026

Search Tags:#architecture #documentation #onboarding #code #data-flow #explain

Ready to run

npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill explain-heaptracetechnology

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/explain
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill explain-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep-dive explanations of code, systems, or features to reveal how they work, why they were built that way, how data flows, what depends on them, and what would break if changed. Use when onboarding, exploring unfamiliar code, or before modifying something you don't fully understand.

Core Features & Use Cases

Structured, big-picture explanations that scale to juniors and seniors
Step-by-step tracing of data flow across components and boundaries
Clear rationale and design decisions to support onboarding and code reviews
Comprehensive guide suitable for unfamiliar code and future modifications

Quick Start

Provide the codebase or target file, and this skill will generate a detailed, actionable explanation covering architecture, data flow, and potential risks.

Frequently Asked Questions about explain

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

FAQPage Schema

How do I explain complex code architecture to accelerate developer onboarding?▼

To explain complex code architecture for onboarding, provide the codebase or target file to generate a detailed explanation covering structured big-picture intros, step-by-step data flow tracing across boundaries, and clear design rationale.

What is the best way to trace data flow across components in unfamiliar code?▼

The best way to trace data flow in unfamiliar code is to map step-by-step data paths across component boundaries. This identifies system dependencies, reveals behavioral logic, and highlights exactly what would break if specific features are modified.

Can I use this to understand code rationale before modifying features?▼

Yes, you can use it to understand code rationale before modifying features. It enforces rationale-focused explanations of design decisions and maps dependencies to ensure you fully grasp system behavior and potential breakage risks before making changes.

Does this approach work for exploring both high-level architecture and specific component behavior?▼

Yes, it scales for both high-level architecture and specific component behavior. It enforces a big-picture intro while simultaneously tracing detailed data-path logic across components, making it suitable for both junior and senior developers.

What do I need to provide to generate a detailed code explanation?▼

You need to provide the codebase or target file. The system then generates a detailed, actionable explanation covering the architecture, data flow paths, design rationale, and potential modification risks associated with the system.

When should I use a structured code explanation tool for unfamiliar codebases?▼

Use a structured code explanation tool during onboarding, when exploring unfamiliar code, or before modifying features you don't fully understand. It maps data flows and dependencies to reveal exactly what would break if the system is changed.