From explain
Explain code. Default is a one-sentence summary plus a mental model. Add `verbose` to also get an ASCII diagram, key details, and a modification guide.
npx claudepluginhub poshan0126/dotclaude --plugin explain[target] [verbose?]This skill uses the workspace's default tool permissions.
Explain `$ARGUMENTS` clearly.
Explains complex code, algorithms, and systems via narratives, visual diagrams, and step-by-step breakdowns. Use for onboarding, learning materials, and debugging reasoning.
Explains complex code, algorithms, system behaviors, and architectures with narratives, visual diagrams, and step-by-step breakdowns for onboarding, learning, and debugging reasoning.
Explains complex code using narratives, Mermaid diagrams, and step-by-step breakdowns. Ideal for algorithms, design patterns, functions, and walkthroughs.
Share bugs, ideas, or general feedback.
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?