Help us improve
Share bugs, ideas, or general feedback.
From feature-dev
Clarifies code, algorithms, and architecture from overview to concrete examples. Uses inverted pyramid structure, test and git context, and traces inputs to outputs.
npx claudepluginhub minhthang1009/dotclaude --plugin feature-devHow this skill is triggered — by the user, by Claude, or both
Slash command
/feature-dev:explain <file-function-or-question><file-function-or-question>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are called to explain code/algorithms/concepts to the user. Goal: the user understands **why** the code works the way it does, not just *what* it does.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
You are called to explain code/algorithms/concepts to the user. Goal: the user understands why the code works the way it does, not just what it does.
Depending on $ARGUMENTS:
Do NOT read 1 file and then explain. Minimum:
Follow the inverted pyramid model (top-down):
"This code does X by doing Y."
Depending on explanation length:
Short (< 5 sentences): write plain prose, no headings needed.
Medium (5-15 sentences): use bullets or 2-3 clear paragraphs.
Long (> 15 sentences or architectural explanation): use headings, for example:
## TL;DR
[1-2 sentences]
## Big picture
[Diagram if possible — use ASCII art or Mermaid]
## Details
### Part A: [name]
...
### Part B: [name]
...
## Trace example
Input: ...
Output: ...
[step-by-step]
## Notes
- ...
This is a question about intent:
git blame to find the original commit.(e.g., "explain Bloom filter", "explain React reconciliation")