code-explainer
Explain what a piece of code does in plain English, at the depth the reader needs. Use when asked to explain code, walk through a function, understand an unfamiliar snippet, or onboard to a file. Produces a one-line summary, a step-by-step walkthrough, the non-obvious parts called out, and any bugs or smells spotted along the way.
npx skills add mohitagw15856/pm-claude-skills --skill code-explainer --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.
# Code Explainer Skill Make unfamiliar code understandable — fast — without dumbing it down. ## Working from a brief Infer the language and intent from the code itself; label assumptions *(assumed — confirm)*. Always produce a complete explanation even from a fragment. Match depth to the apparent level of the question. ## Input The code snippet or file, plus (if given) the language, the reader's level, and what they're trying to understand. Infer the rest. ## Output Structure ### In one line What this code does, in a single sentence a busy reader can repeat. ### Step by step A walkthrough of the logic in order — group by block/function. Explain *why*, not just *what*, for anything non-trivial. Reference line ranges where helpful. ### Worth knowing The non-obvious bits: clever tricks, gotchas, side effects, complexity, dependencies, or assumptions the code makes. ### Anything off? Bugs, edge cases, or smells you noticed while reading — with the fix. (If it's clean, say so.) ## Quality Checks - [ ] The one-line summary stands alone - [ ] The walkthrough explains *why*, not just restating the code in words - [ ] Non-obvious behaviour (side effects, complexity, edge cases) is surfaced
- Working from a brief
- Input
- Output Structure
- In one line
- Step by step
- Worth knowing
- Anything off?
- Quality Checks
- Anti-Patterns
What does the code-explainer skill do?
Explain what a piece of code does in plain English, at the depth the reader needs. Use when asked to explain code, walk through a function, understand an unfamiliar snippet, or onboard to a file. Produces a one-line summary, a step-by-step walkthrough, the non-obvious parts called out, and any bugs or smells spotted along the way.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill code-explainer --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 mohitagw15856/pm-claude-skills, a repository with 1,255 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.