Skip to content

rse/ase / plugin/skills/ase-code-insight

ase-code-insight

Unverified

Give insights into the source code.

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

<if condition="<ase-project-boxing/> is equal `black`">

The project source artifacts are classified as a *black box*, so the
user does *not* want them inspected or their internals surfaced.
*Skip* the entire insight gathering: do *not* read any source, only
output the following <template/> and then *SKIP* the remaining steps
STEP 2 through STEP 4:

<template>
<ase-tpl-bullet-normal/> **PROJECT INSIGHT**: *suppressed* (`project.boxing` is `black`)
</template>

</if>

Determine an <abstract/> summary of this project.
For this, check a potentially existing `README.*` file
or scan the source files of <getopt-arguments/> and figure it out
indirectly.

Display the results with the following <template/>:

<template>
<ase-tpl-bullet-normal/> **PROJECT ABSTRACT**:

<abstract/>
</template>
</step>

2. Determine the of this project. For this, run the following command...

```
git shortlog -sn --no-merges HEAD
```

...and then display the results with the following <template/>:

<template>
<ase-tpl-bullet-normal/> **PROJECT AUTHOR**:

<author/>
</template>
</step>

3. Display the source files of which caused the most churn by figuring out which of them have the most commits. Display the following :

<template>
<ase-tpl-bullet-normal/> **SOURCE CHURN**:
</template>

Then run the following command...

```
git log --format=format: --name-only --since="1 year ago" -- <getopt-arguments/> | grep -v '^$' | sort | uniq -c | sort -nr | head -10
```

...and then display its result as a table with a table head and
columns named "Commits" and "Source File". Do not display any
further explanation of this result.
</step>

4. Display the following :

<template>
<ase-tpl-bullet-normal/> **MODULE STRUCTURE**:
</template>

Find all modules (or OOP classes) of <getopt-arguments/> and build a
Mermaid specification <mermaid-spec/> for a `flowchart TB` diagram
with all modules as boxes and the imports between modules as the
directed edges. Then render <mermaid-spec/> according to the
*Diagrams* rule of the skill conventions. Do not display any
further explanation except for this diagram.
</step>
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 implementationStars: 318kUpdated Claude CodeCodexUnverifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexUnverifiedInstall
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 fallbackStars: 318kUpdated Claude CodeCodexUnverifiedInstall
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 alwaysStars: 318kUpdated Claude CodeCodexUnverifiedInstall