Explain
Explain a file, function, or recent diff in plain language — what it does, how it flows, and why. Use when the user asks to explain code, says "what does this do", "walk me through this file", "help me understand this", "explain the diff", or is onboarding to unfamiliar code.
Install
$ agentstack add skill-pradnyeshp-claude-skills-explain ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-pradnyeshp-claude-skills-explain) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Recent diff (used when the user asks to explain "the diff" or "the changes")
!git diff HEAD --stat 2>/dev/null || echo "No git changes detected"
Instructions
Explain the target the user named in $ARGUMENTS (a file path, a function/symbol name, or "diff"/"changes" to explain recent edits). If no target was given, ask what they'd like explained.
Approach
- Read before explaining. Open the relevant file(s). For a symbol, use Grep to find its definition and key call sites. For "diff", run
git diff HEADand explain those changes. - Lead with a one-sentence summary of what the code does and why it exists.
- Then give a structured walkthrough:
- Inputs and outputs (parameters, return values, side effects)
- The main control flow, step by step
- Key data structures or algorithms involved
- External dependencies it touches (DB, network, files, other modules)
- Call out anything non-obvious or surprising — implicit assumptions, edge-case handling, performance characteristics, or footguns.
- If the code looks buggy or fragile, note it briefly at the end, but don't turn this into a full review.
Rules
- Match the explanation depth to the audience — assume a competent engineer new to this codebase, not new to programming.
- Reference real symbols and
file:linelocations; don't speak in generalities. - Use short paragraphs and bullet points. Include a tiny annotated snippet only when it clarifies a tricky part.
- Do not modify any files — this skill is read-only.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Pradnyeshp
- Source: Pradnyeshp/Claude-Skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.