Explaining code

Explain a specific change or piece of code to a reader new to it, at the Brief or Full depth.

When the question is how a whole subsystem works (its architecture, data flow, and file map), call the Skill tool with explaining-architecture instead. If that skill is not installed, explain at the chosen depth, scoped to the question. Without a Skill tool, follow the skill call rules.

Input

The request holds an optional depth token followed by the subject: a PR number or URL, a file path, a function or class name, a branch name, or a concept.

STOP when the request names no subject and the conversation makes none clear. Ask once what to explain, and do no work until the user answers.