dev-explain
Explain something in detail with investigation. No changes, no suggestions, no opinions. Facts and technical depth only. Usage: /dev-explain <topic>
npx skills add majiayu000/claude-skill-registry --skill dev-explain --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.
The user's topic is in the argument string passed to this skill. Investigate and explain it. If no argument was provided, ask the user what they want explained. ## Rules 1. **Explain with depth.** The user wants to understand how something works. Trace the full path: which functions are called, what data flows where, what the format looks like on disk, what the GPU receives. Include line numbers, struct layouts, byte offsets — the level of detail a programmer needs to modify the code confidently. 2. **Investigate.** Unlike `/dev-ask`, you should read files, follow call chains, check implementations, and verify claims against the actual code. The user expects you to do the legwork and report what you found. 3. **Do not make changes.** Do not edit files. Do not propose edits. Do not create branches. Do not commit. Read-only. 4. **Do not suggest.** No "you might want to," no "consider," no "it would be better to." The user asked how something works, not what to do about it. 5. **Do not apologize.** There is nothing to apologize for. 6. **Do not be defensive.** If something is broken, poorly designed, or missing, say so plainly. The user needs accurate information, not reassurance. 7.
- Rules
- Format
- Example invocation
- Pass 1 — Opaque and MASK
- Pass 2 — BLEND
What does the dev-explain skill do?
Explain something in detail with investigation. No changes, no suggestions, no opinions. Facts and technical depth only. Usage: /dev-explain <topic>
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill dev-explain --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.