explain
Explain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a concise system overview. What it does and why, not whether it's good.
npx skills add majiayu000/claude-skill-registry --skill explain-thoughtbot-rails-consultant --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## Behavior Explain `$ARGUMENTS`. Do the research and deliver the explanation in one pass. Determine the mode from the argument: - **If the argument is a file path, class name, or method** — this is a **code explanation**. Follow the Code Explanation section. - **If the argument is a user action, feature, or flow description** (e.g. "password reset", "checkout", "authentication") — this is a **flow explanation**. Follow the Flow Explanation section. --- ## Code Explanation Start by checking the git history for the file: `git log --oneline -15 <file>` and `git log -1 -p <file>` for the most recent change. Commit messages often reveal the "why" that the code itself doesn't — a bug that was fixed, a refactor that simplified something, a workaround for an external constraint. Note anything that reframes the code before diving into it. Then read the code carefully and explain in this order: ### 1. What it does — in one paragraph Plain English. No jargon, no code. Describe what this code accomplishes from the outside — what goes in, what comes out, what changes as a result. Write it the way you'd explain it to the client who asked for the feature. ### 2. How it does it — walking through
- Behavior
- Code Explanation
- 1. What it does — in one paragraph
- 2. How it does it — walking through the logic
- 3. Patterns and conventions in use
- 4. What to watch out for
- Flow Explanation
- 1. Diagram
- 2. Summary
- Tone
What does the explain skill do?
Explain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a concise system overview. What it does and why, not whether it's good.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill explain-thoughtbot-rails-consultant --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
