explain

Select the code or name the area you want to understand and ask how it works. The explanation covers what the code does, a step-by-step walkthrough of its logic, and design rationale when relevant.

Every explanation includes a one-sentence summary of what the code does and a step-by-step walkthrough of how it works. When relevant, it also covers design rationale, key dependencies, and non-obvious gotchas or edge cases.

Yes, it checks git blame and commit history to uncover historical context behind non-obvious decisions. For legacy or unusual code, it prioritizes explaining the original author's intent over pure mechanics.

Use explain when you only want to understand how code behaves, including code that errors or throws. If your goal is to fix a failure or find its root cause, use the debug skill instead.

Yes, explanations are calibrated to your apparent expertise. Senior engineers get concise architectural context without basic fundamentals, while newcomers receive more foundational detail without assumed domain knowledge.