analyze
無料Risk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Meta-orchestrator — dispatches to the right skill for the task. Use before any non-trivial work.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Graph evidence uses codebase-memory-mcp scoped by CBM_PROJECT. Orientation
loads get_architecture aspects overview, layers, boundaries, clusters,
and hotspots, plus validated hubs, bridges, and test-gaps recipes. If
optional graph evidence is unavailable, label it unavailable and use Serena or
filesystem evidence.
Dispatch to the right skill. 1% rule: if it might apply, invoke it.
| User intent | Skill to invoke |
|---|---|
| "start", "begin", unclear scope | /supergraph:analyze |
| "plan", "lên kế hoạch", explicit plan request | /supergraph:plan |
| "implement", "build", "execute" (plan saved) | /supergraph:execute |
| "fix bug", "debug", "why failing" | /supergraph:fix |
| "test", "TDD", "add tests" | /supergraph:tdd |
| "refactor", "clean up", "reorganize" | /supergraph:plan (then execute) |
| integration/e2e tests, after unit green | /supergraph:integration |
| "done?", "verify", before commit/PR | /supergraph:verify |
| "review", "merge", "PR", before merge | /supergraph:review |
| Need project context | /supergraph:scan |
/supergraph:tdd directly/supergraph:plan with lightweight tasks/supergraph:analyze first, then plan"Add X" or "Fix Y" is the WHAT. Skills determine HOW. Never skip a skill because the task "feels simple."
All skills depend on /supergraph:scan being loaded first in the session.
When dispatching subagents (executor, code-reviewer, plan-writer, plan-reviewer):
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Risk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Proactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.
日本語の概要は準備中です。原文の説明を表示しています。
Persistent token-compression mode (~75% reduction) — now always-on by default. Strips filler while keeping code exact.
日本語の概要は準備中です。原文の説明を表示しています。
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
日本語の概要は準備中です。原文の説明を表示しています。
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
日本語の概要は準備中です。原文の説明を表示しています。
Structured 6-phase debugging. Build feedback loop first, reproduce deterministically, hypothesize with ranked falsifiable theories, instrument one variable at a time, fix with regression test, cleanup. Use when a bug exists, tests fail unexpectedly, or behavior is wrong and cause is unknown.
日本語の概要は準備中です。原文の説明を表示しています。