Ase Code Explain

@${CLAUDESKILLDIR}/../../meta/ase-control.md @${CLAUDESKILLDIR}/../../meta/ase-skill.md @${CLAUDESKILLDIR}/../../meta/ase-getopt.md

Explain Source Code

$ARGUMENTS

Analyze the source code of , and its directly related source code and explain it in a brief, standardized, and concise way.

Investigate the code. If the code base is large, you MUST use the Agent tool (not inline work) to create multiple sub-agents to split the investigation task into appropriate chunks.

Explain the WHAT and WHY.

First, explain WHAT the code does (functionality). Second, explain WHY the code does it (rationale).

Keep your explanations brief and concise. Output the result with the following :

WHAT (You should know what):

• [...]
• [...]
• [...]

WHY (You should know why):

• [...]
• [...]
• [...]

Give insights with ANALOGY and DIAGRAM.

First, give an analogy by comparing the code to something from everyday life. How can I understand this by something I already know? Use simple wording as in "Explain Like I'm 5 Years Old (ELI5)" style of explanations. For very complex concepts, use multiple analogies.

Second, draw a diagram to show the control or data flow, code or data structure, or code or data relationships. What gives the best overall overview of the code? Build a Mermaid specification , choosing the Mermaid diagram type per intent: classDiagram for class/method structure, sequenceDiagram for actor/message flow, or flowchart TB for boxes-and-lines component layouts. Then dispatch the rendering to the ase-meta-diagram sub-agent by calling the tool Agent(name: "ase-meta-diagram", description: "Diagram Rendering", subagent_type: "ase:ase-meta-diagram", prompt: ) and reproduce its returned fenced code block verbatim in the response text. Do not hand-draw.

Keep your explanation brief and concise. Output the result with the following :

ANALOGY (You should imagine):

• [...]
• [...]
• [...]

DIAGRAM (You should grasp): [...]

Highlight CRUXES and GOTCHAS.

First, tell what are the cruxes of the code. Is there something one should really notice?

Second, tell what are the gotchas of the code. Is there something one could really stumble over?

Keep your explanation brief and concise. Output the result with the following :

CRUXES (You should notice):

• [...]
• [...]
• [...]

GOTCHAS (You should not stumble over):

• [...]
• [...]
• [...]

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: rse
• Source: rse/ase
• License: Apache-2.0
• Homepage: https://ase.tools

Install and usage instructions live in the source repository linked above.