Stats
Actions
Tags
From explain
Explains code snippets: one-sentence summary and mental model by default; verbose adds ASCII diagram, key details, and modification guide.
How this skill is triggered — by the user, by Claude, or both
Slash command
/explain:explain [target] [verbose?][target] [verbose?]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Explain `$ARGUMENTS` clearly.
Explain $ARGUMENTS clearly.
If $ARGUMENTS includes the word verbose (for example, /explain my-function verbose), produce all five sections below. Strip the word verbose from the target name when interpreting what to explain.
Otherwise (the default), produce only sections 1 and 2 and stop. Day-to-day that's usually all you need.
What does it do, and why does it exist? One sentence.
An analogy or metaphor that captures the core idea. Relate it to something the developer already knows. One short paragraph.
Draw an ASCII diagram showing the data and control flow. Keep it readable:
Input -> [Step A] -> [Step B] -> Output
|
v
[Side Effect]
Walk through the important parts. Skip the obvious. Focus on:
What would someone need to know to safely change this code? Where are the landmines?
npx claudepluginhub poshan0126/dotclaude --plugin explainExplains complex code using narratives, Mermaid diagrams, and step-by-step breakdowns. Ideal for algorithms, design patterns, functions, and walkthroughs.
Explains code using visual diagrams, analogies, and step-by-step walkthroughs. Use when teaching a codebase or answering 'how does this work?'
Explains complex code, algorithms, system behaviors, and architectures with narratives, visual diagrams, and step-by-step breakdowns for all developer levels.