← ClaudeAtlas

explain-codelisted

Explains unfamiliar code the way a senior engineer walks a colleague through it — purpose, inputs, outputs, execution flow, dependencies, external services, data flow, failure modes, error handling, gotchas, improvements, tests, how to run and debug it, and a guided code tour, all grounded in the actual repository with file/line references and a clear split between confirmed, inferred and unknown. Draws architecture, sequence, data-flow, error-path and state diagrams; can produce a rendered visual HTML report (--visual) or a saved Markdown report with Mermaid (--save), a short version (--brief), a worked example that follows one concrete input through the code (--example), or explain what a change, branch or PR does (--diff). Works for any language, framework or architecture and any scope from a single function to an entire repository. Read-only — never modifies the code. Use when the user runs /explain-code or asks to explain, diagram, walk through, onboard onto, or understand how some code, feature, change
raj-wankhede-github/claude-skill-explain-code · ★ 0 · Data & Documents · score 70
Install: claude install-skill raj-wankhede-github/claude-skill-explain-code
# /explain-code — a senior engineer's walkthrough of unfamiliar code **Request:** $ARGUMENTS !`python ${CLAUDE_SKILL_DIR}/scripts/repo_context.py || python3 ${CLAUDE_SKILL_DIR}/scripts/repo_context.py || echo "## Repository snapshot: unavailable (no Python found). Gather branch, commit, remote, uncommitted changes and top-level layout with read-only git and Glob."` Your job: help a developer understand code they have never seen, well enough to modify it tomorrow. Explain *this* code in *this* repository — not programming in general. Every important claim must trace back to a file and symbol the developer can open. Accuracy beats sounding confident. If you did not read it, you do not know it. ## Hard rules 1. **Read-only.** Do not edit, create, refactor, reformat or delete files in the repository. Do not install dependencies, change configuration, run migrations, start services, run tests, or run anything that writes or has side effects. Reading, searching, and read-only git commands are fine (the ones in `allowed-tools` run without a prompt; anything else asks the user). The **only** file this skill ever writes is the report requested with `--visual` or `--save`, and it goes **outside the repository** unless the user gave a path (Step 7). 2. **Never reveal secrets.** If you meet credentials, tokens, keys, connection strings with passwords, or private certificates, say *that* they exist and *where* (`.env` defines `STRIPE_API_KEY`), never their value