ase-code-explain

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md <skill name="ase-code-explain"> Explain Source Code </skill> <expand name="getopt" arg1="ase-code-explain"> $ARGUMENTS </expand> <objective> *Analyze* the source code of <getopt-arguments/>, and its directly related source code and *explain* it in a *brief*, *standardized*, and *concise* way. </objective> <flow> 1. <step id="STEP 1: Investigate Code Base"> 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. </step> 2. <step id="STEP 2: WHAT and WHY"> **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*. <if condition="<ase-project-boxing/> is equal `black`"> 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 <template/>: <template> <ase-tpl-bullet-normal/> **WHAT** (You should know what): - [...] - [...] - [...] </template> </if> <else> Output the result with the following <template/>: <template> <ase-tpl-bullet-normal/> **WHAT** (...