rse/ase / plugin/skills/ase-code-explain
ase-code-explain
UnverifiedExplains code with WHAT, WHY, ANALOGY, DIAGRAM, CRUXES, and GOTCHAS. Use when you want to know how code works or when the user asks "how does this work?"
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
-
First, explain WHAT the code does (functionality). Second, explain WHY the code does it (rationale).
Keep your explanations brief and concise.
The project source artifacts are classified as a black box, so the user wants only the minimal surface explanation. Output only the WHAT block (omit the WHY block) with the following :
Output the result with the following :
WHY (You should know why):
- [...]
- [...]
- [...]
-
The project source artifacts are classified as a black box, so deeper elaboration is not wanted. Skip this STEP 3 and the following STEP 4 entirely: do not output any ANALOGY, DIAGRAM, CRUXES, or GOTCHAS, and do not dispatch any diagram rendering.
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:
classDiagramfor class/method structure,sequenceDiagramfor actor/message flow, orflowchart TBfor boxes-and-lines component layouts. Then render at the position of the diagram in the response according to the Diagrams rule of the skill conventions. Do not hand-draw.Keep your explanation brief and concise. Output the result with the following :
DIAGRAM (You should grasp): [...]
-
First, tell what the cruxes of the code are. Is there something one should really notice?
Second, tell what the gotchas of the code are. Is there something one could really stumble over?
Keep your explanation brief and concise. Output the result with the following :
GOTCHAS (You should not stumble over):
- [...]
- [...]
- [...]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |