explain-code
Skill833 starsChanged 9 months agoApache-2.0View on GitHub
Explain what code does in plain English
48 other projects use a version of this.
Adopted by
Most recently taken up by
- bradydwardai/claude-skillstheir own version, first seen Nov 8, 2026
- renzrollon/interlocktheir own version, first seen Nov 5, 2026
- jorgenschaefer/skillstheir own version, first seen Nov 1, 2026
- sergerad/skillstheir own version, first seen Nov 1, 2026
- rpraharaj/ai-sdlctheir own version, first seen Nov 1, 2026
- datnt97/claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use explore-codebase, write-tests and 10 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
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 6 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
- silvainfmSkill
pricing-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
- SentrySkill
marketing-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
- +1 more from getsentry
Other versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 48
- renzrollon/interlock★ 61same name
- Integralist/agent-skills★ 23same 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
- Akindu23/my-agent-skills★ 4same name
38 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 repository5 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 41 edited versions we read keep these.
5
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
- Very specific: line 18
Read .claude/PROJECT_CONTEXT.md to understand AgnosticUI's architecture
- Distinctive: line 24
Read the specified file(s)
- Distinctive: line 25
Use Grep/Glob to find related files if needed:
- Distinctive: line 26
If explaining core component, show framework usage examples
- Distinctive: line 27
If explaining framework story, reference core component
- Distinctive: line 28
If explaining utility, show where it's used
“Common” is measured: kept by at least 6 in 10 of the 41 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
Usage: /explain-code PATH_OR_DESCRIPTION
Examples:
/explain-code v2/lib/src/components/Button.ts/explain-code the button ripple effect/explain-code design token system
Explain: $ARGUMENTS
Setup:
- Read
.claude/PROJECT_CONTEXT.mdto understand AgnosticUI's architecture
Process:
- Locate and read the code:
- Identify if it's a core component, framework implementation, or utility
- Read the specified file(s)
- Use Grep/Glob to find related files if needed:
- If explaining core component, show framework usage examples
- If explaining framework story, reference core component
- If explaining utility, show where it's used
- Understand the context:
- Where does this fit in AgnosticUI's architecture?
- Is it framework-agnostic or framework-specific?
- Does it use design tokens or CSS custom properties?
- Are there related files in other frameworks?
- Explain clearly:
- What it does (high level, user-facing behavior)
- How it works (key logic, algorithms, patterns)
- Why it's structured this way (architectural decisions)
- AgnosticUI-specific context:
- How it fits the CSS-first approach
- Framework-agnostic vs framework-specific aspects
- Design token usage
- Accessibility considerations
- Common usage patterns with examples
- Edge cases or gotchas to be aware of
- Provide helpful context:
- Show where it's used (examples, stories, playgrounds)
- Note framework differences if applicable
- Link to related components or utilities
- Reference relevant playbooks if they exist
Keep explanations:
- Clear and jargon-free (or explain jargon)
- Organized from high-level to details
- Focused on understanding, not just describing
- Contextualized within AgnosticUI's multi-framework architecture
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.