explain

Explain code with a summary, analogy-based mental model, and optional verbose deep dive.

1|Updated May 27, 2026
One-click install
npx skills add https://github.com/findexu/finpack-claude --skill explain-findexu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/findexu/finpack-claude/tree/main/plugins/explain/skills/explain
Command: npx skills add https://github.com/findexu/finpack-claude --skill explain-findexu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly understand unfamiliar code by turning it into a concise explanation, including an intuitive mental model and, when requested, a deeper breakdown.

Core Features & Use Cases

  • One-sentence summary that captures what the code does and why it exists.
  • Mental model using an analogy to explain the underlying idea in familiar terms.
  • Verbose deep dive that adds a visual ASCII diagram, key non-obvious details, and safe guidance for modifying the code.

Quick Start

Use the explain skill to explain a target like your function or module by running /explain <target>.

Frequently Asked Questions about explain

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

FAQPage Schema
How do I understand unfamiliar code in an existing codebase?

To understand unfamiliar code, generate a concise summary and an analogy-based mental model of the target function or module, clarifying its intent and flow without reading every line.

What is the best way to create a mental model for debugging complex modules?

Creating a mental model for debugging complex modules involves translating code logic into familiar analogies, optionally adding ASCII diagrams and deep-dive details to visualize non-obvious interactions and structure.

How do I safely refactor code I didn't write?

To safely refactor code you didn't write, first generate a verbose deep-dive breakdown to understand the underlying intent, flow, and key non-obvious details, which provides guidance for making safe modifications.

Can I get a visual diagram when reviewing pull-request changes?

Yes, you can get a visual diagram when reviewing pull-request changes by requesting a verbose deep dive, which adds an ASCII diagram to the summary and mental model to visualize the code structure.

Does the code explanation include guidance for modifying the target module?

Yes, the code explanation includes guidance for modifying the target module when the verbose mode is used, adding safe refactoring tips alongside the visual ASCII diagram and key non-obvious details.