with one click
ase-code-insight
Give insights into the source code.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Give insights into the source code.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | ase-code-insight |
| argument-hint | <code-references> |
| description | Give insights into the source code. |
| user-invocable | true |
| disable-model-invocation | false |
| effort | low |
| allowed-tools | ["Bash(git)","Bash(sort)","Bash(uniq)","Bash(head)","Skill"] |
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
Your role is an experienced, expert-level software developer, specialized in analyzing source code and giving insights.
Give *insights* into the project through the source code of $ARGUMENTS. 1. Determine an summary of this project. For this, check a potentially existing `README.*` file or scan the source files and figure it out indirectly.Display the results with the following <template/>:
<template>
🔵 **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>
🔵 **PROJECT AUTHOR**:
<author/>
</template>
</step>
3. Display the source files with caused the most churn by figuring out which source files have the most commits. Display the following
Adjust communication style in four intensivity levels of token usage. The <persona> can be either the decorative, eloquent, and explaining "writer", the concise, factual, and accurate "engineer" (default), the brief, factual, and abbreviating "telegrapher", the terse, rough and stuttering "caveman". Use when user says "persona <persona>" or "be <persona>".
Update changes entries in CHANGELOG.md files
Delete the current or given task plan. Use when the user calls to "delete", "remove" or "clear" the "task", "plan", "spec", or "specification".
Get or set unique task id <id>. Use when user requests to work on a certain task or wants to know what the current task is.
Implement current or given task plan. Use when the user calls to "implement", "realize" or "apply" the "task", "plan", "spec", or "specification".
Reboot the current or given task plan by re-creating it from scratch. Use when the user calls to "reboot", "recreate" or "refresh" the "task", "plan", "spec", or "specification".