← ClaudeAtlas

explain-yourselflisted

Explain a code file, directory, pull request, commit, or diff, spoken aloud by default when the tts skill is installed, in writing otherwise. Matches the explanation to what it's explaining, a PR/commit/diff gets a file-by-file walkthrough of what changed and why (not a code listing); a file or directory gets a top-down explanation (structure, then how the pieces interact, then the details that matter), with exact code shown only where necessary. Adapts to stated context like "I'm a novice in Terraform." Use when the user wants a PR/commit/diff/file/directory explained, walked through, or summarized, or wants to listen to one. For a document that's already prose, use the tts skill directly.
ArunskiOrg/BenArunskiUtils · ★ 1 · AI & Automation · score 70
Install: claude install-skill ArunskiOrg/BenArunskiUtils
# Explain yourself! — code and change explanations, written or spoken Turns a code file, directory, pull request, commit, or diff into an explanation shaped to match what it's explaining, not a transcription of it. The explanation is spoken aloud, via the [`tts`](../tts/SKILL.md) skill, whenever `tts` is installed; without it the same explanation is delivered as text. ## Requirements - `git` on PATH for commit sources; `gh` on PATH and authenticated for pull request sources. - Python 3.9+ to run `scripts/resolve_source.py`. - The `tts` skill, installed as a sibling skill, for the default spoken output (see this repo's root README for the install path). Without it this skill still works, text only. What this skill executes, sends over the network, and writes to disk is disclosed in [README.md, "Permissions and network egress"](README.md#permissions-and-network-egress). ## Inputs 1. **Source** — one of, resolved in this order: - Pull request: a number (`482`) or URL - Commit: a SHA or ref - Diff file: a path ending `.diff` or `.patch` - Directory: a folder path — explains its immediate files, not subdirectories - Code: a file path, optionally `path:START-END` for a line range If the argument is missing or fits more than one form, ask which it is. 2. **Context** (optional) — if the request names the reader's background or what to focus on ("I'm a novice in Terraform," "focus on the API layer"), capture it verbatim. Otherwise leave it empty; don't ask for it