From ase
Analyze the source code for problems in the logic and semantics and its related control flow.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ase:ase-code-analyze [--help|-h] <source-reference>[--help|-h] <source-reference>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
Analyze Source Code *Analyze* the source code of $ARGUMENTS, and its directly related source code, for problems in its *logic* and *semantics* and its related *control flow*.Tenets:
Quiet Operation: During investigation in this STEP 1, do not output anything else, especially do not give any further explanations or information.
Practical Relevance Only: Focus on practically relevant cases and especially do not investigate theoretical or fictive cases.
Problem Focus Only: Still focus on the problem only and do not already investigate any possible solution.
npx claudepluginhub rse/ase --plugin aseCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.