explain-code
Skill1 starsChanged 3 months agoMITView on GitHub
Explain how existing code works, without changing it. Use when the user wants to understand something — "explain X", "how does X work", "walk me through X", "what does this do", "why is X written this way", "help me understand X", "what's going on in X". Use it for any request to understand code rather than modify it.
54 other projects use a version of this.
Adopted by
Most recently taken up by
- MatthewDelprado/claude-skillstheir own version, first seen Nov 16, 2026
- mlschodkowski/skillstheir own version, first seen Nov 16, 2026
- raj-wankhede-github/claude-skill-explain-codetheir own version, first seen Nov 15, 2026
- netarz/gisoo-skills-registrytheir own version, first seen Nov 15, 2026
- jameswyse/skillstheir own version, first seen Nov 15, 2026
- bradydwardai/claude-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use explore-codebase, copy-editing and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
srclightSkillexplore-codebase
This skill should be used when the user asks to "explore this codebase", "understand this project", "give me an overview", "how does this work", "onboard me", "walk me through the architecture", "map the codebase", or any request to understand a codebase's structure, architecture, or design.
Also in 3 projects that use this
silvainfmSkillcopy-editing
When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.
Also in 3 projects that use this
silvainfmSkillpricing-strategy
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy.
Also in 3 projects that use this
SentrySkillmarketing-psychology
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.
Also in 3 projects that use this
Google CloudSkillopen-pr
Commits local changes to a new Git branch and opens a GitHub pull request through the configured GitHub MCP server. Use when proposing code changes in a new pull request. Don't use for local-only commits without a remote GitHub repository.
Also in 3 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 4 projects that use this
Other versions54 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 54
- AgnosticUI/agnosticui★ 832same name
- renzrollon/interlock★ 62same name
- Integralist/agent-skills★ 29same name
- zbruhnke/claude-code-starter★ 16same name
- rommelporras/kiro-config★ 13same name
- sidkh/skills★ 8same name
- bsene/skills★ 7same name
- holt-os/holt★ 7same name
- viknesh20-20/claude-code-tool-kit★ 7same name
- electronx/wiredkits-free★ 5same name
44 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- build-newSkill
- debug-failureSkill
- plan-approachSkill
- review-diffSkill
- update-featureSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 46 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Read the code and everything it calls into.
- Very specific: line 17
Follow the real path — entry point, transformations, exits — and cite file:line at each step so every claim is checkable.
“Common” is measured: kept by at least 6 in 10 of the 46 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Explain this code
Explain: $ARGUMENTS. Default to whatever is on screen or was last discussed.
How to work
- Read the code and everything it calls into. Explain what is there, not what the naming suggests should be there.
- Lead with the one-sentence answer: what this does and why it exists. Then the detail, in the order the reader needs it.
- Follow the real path — entry point, transformations, exits — and cite
file:lineat each step so every claim is checkable. - Cover the parts that surprise: the early return, the retry, the guard that looks redundant, the workaround. Check git history if the reason is not in the code.
Rules
- Change nothing. This is read-only. If you notice a bug, say so at the end and leave the fix to a separate request.
- Say "I don't know" where the code does not say. Do not present a plausible reason for a line as if it were the recorded one.
- Match the depth to the question. "What does this do" wants a paragraph; "walk me through it" wants the path.
- Explain in prose and structure, not by pasting the file back.
Report back
The explanation is the deliverable. End with anything you could not determine, and any bug you noticed while reading.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

