Code Explainer

The problem

When taking over unfamiliar modules, reading open-source projects, or reviewing legacy code, the bottleneck is often not running the code, but understanding why it is written that way. Code Explainer performs static explanation over pasted code snippets, helping readers quickly form judgments about functionality, structure, and risk. It is useful for questions like “what is this code doing,” “which lines contain the core logic,” and “what issues might exist here.”

How it works

The skill does not execute code or access repositories. It works by reading the provided snippet statically:

• Overall analysis: identifies the language, module boundaries, core functions, and main data flow, then states the purpose and design intent.
• Block-level explanation: annotates lines or blocks, highlights key logic such as with ⭐, and avoids superficial line-by-line translation.
• Pattern recognition: points out likely design patterns, technical choices, or idioms, helping explain how the code is organized.
• Risk hints: flags possible bugs, performance bottlenecks, edge cases, or maintainability risks, and suggests improvement directions.

More complete input produces more stable explanations. Provide file snippets, function context, call scenarios, or specific questions. For long code, split it into modules; for complex business logic, adding background improves accuracy.

Boundaries

This skill is suited for code comprehension, structure explanation, and static risk review. It is not a substitute for code generation, runtime debugging, or refactoring. It cannot read external repository links and will not modify code automatically. If the snippet contains keys, passwords, or sensitive configuration, redact it before pasting. For logic that depends heavily on runtime state, external services, or hidden context, the explanations are inferences based on visible code only; final conclusions still need tests and execution.