Function Explainer
Free gateway skill from the Code Explainer bundle by GarphenGate.
One function in, one structured explanation out: the what, the why, and the sharp edges, at reading-in-a-hurry length.
Procedure
- Take the paste, plus optional context (language version, framework, where it is called from). Missing context narrows the claims, it does not stop the explanation.
- State the what in two sentences of plain English: inputs, outputs, and the transformation between them, as observable behavior rather than a line-by-line retelling.
- Infer the why carefully: what problem this function most plausibly solves, labeled as inference unless comments or naming make it explicit.
- Hunt the gotchas in a fixed sweep: edge inputs (empty, null, zero, huge), hidden state or side effects, error behavior (throws, swallows, returns sentinel), performance traps, and anything that behaves differently than the name suggests.
- Deliver the card below; if the function exceeds roughly 50 lines or calls into significant unseen code, say which parts of the explanation are limited by that.
FUNCTION: <name or 'anonymous'>
What: <two sentences, observable behavior>
Why (inferred unless stated): <the problem it solves>
Signature says / behavior does: <match | mismatch: <detail>>
Gotchas:
- <edge case or side effect> - <what happens> - <when it bites>
Unclear without more context: <list - or 'nothing significant'>
One-line summary you could put in a comment: <it>
Rules
- Never retell the code line by line; the explanation is behavior-level or it is not an explanation.
- Never present an inferred purpose as stated fact; the label 'inferred' stays on until evidence removes it.
- Never skip the gotcha sweep even for tiny functions; three-line functions with a hidden mutation are a classic.
- If the pasted code appears mid-refactor or truncated, say so instead of explaining a fragment as a whole.
Degradation
If the language or framework is unrecognized from the paste alone, explain what is structurally certain, ask one identifying question, and hold the gotcha sweep until the runtime semantics are known.
Like this? This is the free gateway skill for Code Explainer by Moltline Studio. The paid listing: https://www.agensi.io/skills/code-explainer-bundle
1---2name: code-explainer3description: Paste one function and get what it does, why it exists, and its gotchas. Use when the learner wants a fast, honest read on a single piece of code.4---56# Function Explainer78*Free gateway skill from the Code Explainer bundle by GarphenGate.*910One function in, one structured explanation out: the what, the why, and the sharp edges, at reading-in-a-hurry length.1112## Procedure13141. **Take the paste,** plus optional context (language version, framework, where it is called from). Missing context narrows the claims, it does not stop the explanation.152. **State the what** in two sentences of plain English: inputs, outputs, and the transformation between them, as observable behavior rather than a line-by-line retelling.163. **Infer the why carefully:** what problem this function most plausibly solves, labeled as inference unless comments or naming make it explicit.174. **Hunt the gotchas** in a fixed sweep: edge inputs (empty, null, zero, huge), hidden state or side effects, error behavior (throws, swallows, returns sentinel), performance traps, and anything that behaves differently than the name suggests.185. **Deliver the card** below; if the function exceeds roughly 50 lines or calls into significant unseen code, say which parts of the explanation are limited by that.1920```21FUNCTION: <name or 'anonymous'>22What: <two sentences, observable behavior>23Why (inferred unless stated): <the problem it solves>24Signature says / behavior does: <match | mismatch: <detail>>25Gotchas:26 - <edge case or side effect> - <what happens> - <when it bites>27Unclear without more context: <list - or 'nothing significant'>28One-line summary you could put in a comment: <it>29```3031## Rules3233- Never retell the code line by line; the explanation is behavior-level or it is not an explanation.34- Never present an inferred purpose as stated fact; the label 'inferred' stays on until evidence removes it.35- Never skip the gotcha sweep even for tiny functions; three-line functions with a hidden mutation are a classic.36- If the pasted code appears mid-refactor or truncated, say so instead of explaining a fragment as a whole.3738## Degradation3940If the language or framework is unrecognized from the paste alone, explain what is structurally certain, ask one identifying question, and hold the gotcha sweep until the runtime semantics are known.414243---4445*Like this? This is the free gateway skill for **Code Explainer** by Moltline Studio. The paid listing: https://www.agensi.io/skills/code-explainer-bundle*
GarphenGate