Explain

Trace data flow and explain code with file and line references.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/nille/shipkit --skill explain-nille
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Explain
Source: https://github.com/nille/shipkit/tree/main/shipkit/core/skills/explain
Command: npx skills add https://github.com/nille/shipkit --skill explain-nille

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explain code, architecture, or system behavior. Use when user says "explain this", "how does this work", "what does this do", "walk me through", or "why is it done this way".

Core Features & Use Cases

  • Reads code and produces clear explanations at the right level of detail.
  • Explains a single function, an entire module, or the project architecture, and how pieces connect.
  • Supports context-aware depth and audience tailoring to different stakeholders.

Quick Start

Explain the architecture of the main module at a standard level.

Frequently Asked Questions about Explain

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

FAQPage Schema
How do I explain code and system architecture clearly to different stakeholders?

To explain how code works, read the target files, trace data flow through relevant execution paths, reference specific files and line numbers, and generate structured explanations using project terminology to clarify system behavior.

What is the best way to understand a full codebase architecture by reading code?

The best way to understand a full codebase architecture is reading code across modules and tracing how pieces connect. This approach applies context-aware depth to single functions, modules, or full project architecture explanations.

Can I trace data flow through specific code paths to debug system behavior?

Yes, you can trace data flow through specific code paths to debug system behavior. The process reads target code, traces data flow through relevant paths, and references files and line numbers to explain code execution.

Does this approach work for explaining a single function as well as an entire module?

Yes, this approach works for explaining a single function as well as an entire module. It supports context-aware depth and audience tailoring across a codebase, adjusting the level of detail appropriately.

How do I generate documentation that walks through module connections and code flow?

To generate documentation that walks through module connections and code flow, read the code and produce structured explanations. It explains how pieces connect and references files and line numbers using project terminology.

When should I use an automated tool to explain unfamiliar code instead of reading it manually?

You should use an automated tool to explain unfamiliar code when you need to quickly understand system behavior, trace data flow across a codebase, or tailor explanations for different stakeholders without manually reading every file.