メニュー
Review a finished change against its plan. Spawns 1 reviewer subagent, reports ship/rework with severity-tagged findings. Use AFTER /code-build.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/alexeyshishin/as-skill --skill code-reviewコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Enrich Obsidian note frontmatter — fill in the aliases, up, down, other fields without moving the note. Use this skill when the user asks to update/fill in a note's frontmatter, add aliases or links (up/down/other), or enrich a note with links — especially for notes in the `00. Входящие` folder. The note stays in place; only the frontmatter fields aliases, up, down, other change. Do not use for a full refactor with relocation — that's what obsidian-refactor-inbox is for.
Analyze and review notes from the inbox (`00. Входящие`) — inspection and reporting only, no file changes. The output is a list of notes with recommendations for category and action. For actually processing them (tags, links, moving) use obsidian-refactor-inbox.
Processes an arbitrary markdown file (article, web clip, transcript, notes, draft note) and turns it into structured knowledge for an Obsidian base using the PARA methodology. The skill extracts atomic entities (concepts, insights, facts), invents logical names for notes, creates a source literature note, and builds wikilinks and frontmatter. Use this skill whenever the user wants to "add this to the knowledge base", "rework this article", "process these notes", "extract the knowledge from this text", "ingest this", "put this in the vault", "put this in the base", or brings a markdown file to save into Obsidian.
SOC 職業分類に基づく
SKILL.md を表示中
| name | code-review |
| description | Review a finished change against its plan. Spawns 1 reviewer subagent, reports ship/rework with severity-tagged findings. Use AFTER /code-build. |
ORCHESTRATOR. One reviewer subagent. Read-only — the reviewer does not fix.
/code-review <slug>
Gather: plan swarm-report/<slug>-plan.md + build report swarm-report/<slug>-build.md
git diff for staged + unstaged, or vs the branch point).Spawn 1 reviewer (Task, general-purpose). Prompt:
Answer TERSE. Read
.claude/agents/reviewer.mdand follow it exactly. Plan: swarm-report/-plan.md Diff below:
Paste the diff INTO the prompt — the reviewer must not re-read the whole repo.
Report the reviewer's verdict + findings verbatim.
If verdict: rework — the findings ARE the input to a /code-build <slug> retry. Do not
auto-fix here; hand them back and let the user decide.