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.
日本語の概要は準備中です。原文の説明を表示しています。
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Library-agnostic Flutter/Dart code review. Graph-first, then checklist.
Announce: "🐦 /supergraph:flutter-dart-code-review — reviewing Flutter/Dart code..."
Use CBM_PROJECT: call get_architecture with hotspots, then validated
hubs, cycles, complexity, cross-boundary, and test-gaps recipes. Apply
the existing Flutter thresholds: build() over 80–100 lines, complexity limits,
10+ dependents, circular DI, unexpected layer coupling, and untested files.
Serena (optional — if available):
mcp__serena__get_diagnostics_for_file(<file>) # type errors, null safety violations
mcp__serena__find_referencing_symbols(<symbol>) # callers of changed public APIs
mcp__serena__find_implementations(<interface>) # subclasses after interface change
Skip if Serena unavailable.
Work through CHECKLIST.md — 15 sections covering: General health · Dart pitfalls · Widgets · State management · Performance · Testing · Accessibility · Platform · Security · Dependencies · Navigation · Error handling · l10n · DI · Static analysis
Focus on areas flagged by step 1 first.
## Flutter/Dart Review
- Graph hotspots: [list/none]
- Serena diagnostics: [issues/clean/skipped]
- Checklist: PASS | ISSUES (list critical items)
- Next: /supergraph:fix → /supergraph:verify
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。