ワンクリックでManusで任意のスキルを実行

ase-code-explain

スター1

フォーク3

更新日2026年5月22日 11:17

Explains 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?"

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

rse

rse/ase

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

ソフトウェア開発者コンピュータ・数学職·SOC 15-1252

SKILL.md

readonly

name	ase-code-explain
argument-hint	[--help\|-h] <source-reference>
description	Explains 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?"
user-invocable	true
disable-model-invocation	false
effort	high
allowed-tools	["Agent"]

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

Explain Source Code $ARGUMENTS *Analyze* the source code of , and its directly related source code and *explain* it in a *brief*, *standardized*, and *concise* way.

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.
**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. Output the result with the following

このリポジトリの他の Skills

同じリポジトリ

ase-meta-persona

rse/ase

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>".

2026-05-231

ase-meta-changes

rse/ase

Update changes entries in CHANGELOG.md files

2026-05-231

ase-task-delete

rse/ase

Delete the current or given task plan. Use when the user calls to "delete", "remove" or "clear" the "task", "plan", "spec", or "specification".

2026-05-231

ase-task-id

rse/ase

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.

2026-05-231

ase-task-implement

rse/ase

Implement current or given task plan. Use when the user calls to "implement", "realize" or "apply" the "task", "plan", "spec", or "specification".

2026-05-231

ase-task-reboot

rse/ase

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".

2026-05-231

name	ase-code-explain
argument-hint	[--help\|-h] <source-reference>
description	Explains 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?"
user-invocable	true
disable-model-invocation	false
effort	high
allowed-tools	["Agent"]

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

Explain Source Code $ARGUMENTS *Analyze* the source code of , and its directly related source code and *explain* it in a *brief*, *standardized*, and *concise* way.

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.
**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. Output the result with the following