explain

Analyze code to explain files, features, or data flows in a Markdown report.

49|9|Updated Feb 16, 2026

Search Tags:#debugging #documentation #code-analysis #references #explain #walkthrough

Ready to run

npx skills add https://github.com/Terryc21/xcode-workflow-skills --skill explain-terryc21

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/Terryc21/xcode-workflow-skills/tree/main/skills/explain
Command: npx skills add https://github.com/Terryc21/xcode-workflow-skills --skill explain-terryc21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide comprehensive explanations of how a file, feature, or data flow operates by analyzing code and presenting a structured walkthrough.

Core Features & Use Cases

In-depth code explanations that map to specific files, features, or data flows
Determine entry points, dependencies, and execution pathways with references
Produce a reproducible Markdown report that documents the explanation

Quick Start

Invoke the /explain command with a file path or feature name to generate a deep-dive explanation.

Frequently Asked Questions about explain

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

FAQPage Schema

How do I generate a code walkthrough for a specific file or feature?▼

To generate a code walkthrough, provide a file path or feature name to analyze source files. The system traces definitions and references to output a structured Markdown report detailing system behavior.

How does code analysis identify execution pathways and data flow dependencies?▼

Code analysis identifies execution pathways by tracing definitions and references across targeted components. It maps entry points and data paths to reveal how a specific feature or data flow operates.

Can I use this to document system behavior for targeted components in a large codebase?▼

Yes, you can document system behavior for targeted components in a large codebase. It analyzes source files to determine dependencies and execution pathways, producing a reproducible Markdown report.

What is the best way to explain how an unfamiliar data flow operates in source code?▼

The best way to explain how an unfamiliar data flow operates is to analyze the source code directly. This traces definitions and references to map execution pathways and output a structured walkthrough.

Do I need specific dependencies to trace definitions and references across targeted components?▼

No specific dependencies are required to trace definitions and references across targeted components. You only need access to the source files to generate the deep-dive explanation and Markdown report.