drafael/coding-harness / skills/explain-code
explain-code
UnverifiedExplain current code behavior, structure, runtime flow, data flow, and component ownership. Use for ordinary walkthroughs, line-by-line explanations, subsystem mental models, and questions about what code does or how it works. Use teach, when explicitly invoked and available, for progressive learning; technical-writing, when available, for substantial standalone documentation; clarify for expectation mismatches or historical intent; code-review for finding problems; refactor-code for structural changes; brainstorm for unresolved future design; and architect, when explicitly invoked and available, for implementation-ready structural design.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.5 KB |
| README.md | markdown | 2.6 KB |
| SKILL.md | skill md | 7.0 KB |
| references/explanation-patterns.md | markdown | 3.3 KB |
| references/exploration-playbook.md | markdown | 3.3 KB |
| references/language-notes.md | markdown | 2.4 KB |
references/language-notes.md
View on GitHub# Language notes
Load this reference only when language semantics are central to the explanation. Explain the constructs used by the target, not every language feature listed here.
## JavaScript and TypeScript
Distinguish compile-time TypeScript types from runtime validation. Explain Promise creation, `async`/`await`, rejection propagation, and fire-and-forget work when relevant. Clarify closure capture, lexical scope, `this` binding, arrow functions, module boundaries, and event-loop scheduling only where they affect behavior.
Do not assume a typed value is validated at runtime.
## Python
Explain generator laziness, comprehensions, decorators, context managers, async functions, and exception flow when used. For classes, clarify method resolution, descriptors, and class-versus-instance state when relevant. Watch for mutable defaults and late-bound closures when they affect the code, but do not turn the explanation into a review.
## Java
Explain generic bounds, type erasure, records, sealed types, pattern matching, annotations, streams, lambdas, and exception flow when used. Distinguish checked and unchecked exceptions. For concurrent code, identify the executor, thread ownership, synchronization, and completion mechanism established by the implementation.
Do not describe an annotation’s behavior without locating its processor, framework contract, or runtime handling.
## Go
Explain implicit interface satisfaction, pointer versus value receivers, goroutine ownership, channel direction, blocking behavior, `select`, `defer`, and explicit error flow when relevant. Clarify whether cancellation comes from a context and where that context is observed.
Do not assume a launched goroutine is safely owned or eventually joined.
## Rust
Explain ownership moves, borrowing, lifetimes, pattern matching, traits, generics, `Option`, `Result`, and error propagation where they shape the flow. For asynchronous code, distinguish futures from execution and identify the runtime or spawn boundary actually used.
Do not frame compiler-enforced safety as proof of domain correctness.
## Other languages
Use the same method: explain only semantics that materially affect control flow, data representation, ownership, errors, or runtime behavior. Verify framework and language-version behavior from repository context or authoritative documentation when it is not evident from the code.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |