explain

Trace code paths with file:line references and ASCII diagrams.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/sQVe/cape --skill explain-sqve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/sQVe/cape/tree/main/skills/explain
Command: npx skills add https://github.com/sQVe/cape --skill explain-sqve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explain code by building understanding progressively — from entry points through data flow to key decisions. It produces a narrative walkthrough with ASCII flow diagrams, not just a file listing. Adapts depth to scope: a function gets a focused explanation, a system gets a layered overview.

Core Features & Use Cases

  • Read the codebase and trace real code paths, anchoring every claim to file:line references.
  • Build progressive explanations from big picture to details, with ASCII diagrams.
  • Adapt depth to the audience and scope (function, module, or system).
  • Offer guided walkthroughs for end-to-end flows and critical data paths.

Quick Start

Ask me to explain a specific function or module, and I will read the code, reference file:line, and walk you through the flow with ASCII diagrams.

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 paths with visual diagrams?

This Skill explains complex code paths by reading your source and generating a narrative with ASCII flow diagrams. It maps entry points and data flow, anchoring every claim to file:line references to show end-to-end behavior.

What is the best way to trace data flow across an entire codebase?

The best way to trace data flow is by mapping component interactions from entry points through key decisions. This Skill builds progressive explanations from big picture to details, adapting its depth to the system scope.

How do I generate a code walkthrough that anchors to file:line references?

To generate a code walkthrough anchored to file:line references, ask the Skill to explain a function or module. It reads the actual source, anchors every claim to file:line references, and uses ASCII diagrams to illustrate connections.

Can I get an architecture overview that adapts depth to scope?

Yes, you can get an architecture overview that adapts depth to scope. A function receives a focused explanation, while a system gets a layered overview with ASCII diagrams illustrating the end-to-end flow.

Why does my code explanation lack traceability to the actual source?

Your code explanation lacks traceability because it does not anchor claims to file:line references. This Skill reads the actual source before explaining, ensuring every detail of the narrative maps directly to the real codebase.