explain-code-flow

Trace a feature's runtime data flow and render it as Mermaid diagram walkthroughs.

9|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/Yassimba/loom --skill explain-code-flow-yassimba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain-code-flow
Source: https://github.com/Yassimba/loom/tree/main/skills/explain-code-flow
Command: npx skills add https://github.com/Yassimba/loom --skill explain-code-flow-yassimba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Understanding how data actually moves through an unfamiliar codebase is slow and error-prone, and ad-hoc explanations often rest on guesses rather than verified code. This Skill produces grounded, diagram-first walkthroughs of a feature's runtime flow with cited file and line references. ## Core Features & Use Cases - Runtime Flow Tracing: Follows the happy path from entry point to output, then traces failures, retries, and background processes as separate flows. - Mermaid Visual Narratives: Builds one focused Mermaid diagram per concept (flowchart, sequence, ER, state, or lineage) with enforced complexity budgets of roughly 9 nodes and 12 arrows per figure. - Verified Evidence: Every node and edge cites an actual file:line you opened, with unverified claims marked as assumptions rather than drawn as fact. - Use Case: Onboarding onto a new service, ask for a walkthrough of the checkout flow and receive sectioned explanations where each diagram precedes the code excerpts it describes, including object lineage and revision diffs with green/red/amber change markers. ## Quick Start Use the explain-code-flow skill to trace how a request moves through the payment module and show the flow as Mermaid diagrams with source references.

Frequently Asked Questions about explain-code-flow

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

FAQPage Schema
How do I explain the flow of a feature in an unfamiliar codebase?

Start at the runtime entry point or public API, identify the data spine that crosses stages, and follow the happy path before adding branches. This Skill automates that process and renders each concept as a focused Mermaid diagram with verified file:line references.

How to create a code walkthrough with Mermaid diagrams?

Write a section outline first, then give each section one fenced mermaid block placed before the code it describes. Keep diagrams to about 10-15 nodes, label edges with the data type or action, and never reproduce complete files.

Can Mermaid diagrams show differences between two code revisions?

Yes. The Skill inspects changed source at both revisions with targeted Git reads, then marks additions with green, removals with red dashed styling, and modifications with amber, each backed by revision-qualified source references.

Does this generate SVG or image files for the diagrams?

No. The walkthrough is delivered in chat as fenced mermaid blocks only. It deliberately does not generate SVG, HTML, or image artifacts, keeping the source code as the single source of truth.

What are the limits on Mermaid diagram complexity?

Each figure is capped at roughly 9 nodes, 12 arrows, 5 sequence lifelines, and 2 callouts. When content exceeds the budget, side branches become callouts or the concept is split into two figures, with cuts reported explicitly.