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.
Scanned 8/31/2026
Install via CLI
openskills install datit309/supergraph---
name: flutter-dart-code-review
description: 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.
mcp: codebase-memory-mcp
---
# /supergraph:flutter-dart-code-review
Library-agnostic Flutter/Dart code review. Graph-first, then checklist.
Announce: "🐦 /supergraph:flutter-dart-code-review — reviewing Flutter/Dart code..."
## Steps
### 1. Graph analysis (surface hotspots before manual review)
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.
### 2. Manual checklist review
Work through [CHECKLIST.md](./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.
### 3. Report
```
## Flutter/Dart Review
- Graph hotspots: [list/none]
- Serena diagnostics: [issues/clean/skipped]
- Checklist: PASS | ISSUES (list critical items)
- Next: /supergraph:fix → /supergraph:verify
```
## Rules
- Run graph analysis before opening checklist — prioritize hotspots
- Serena diagnostics catch null safety / type errors manual review misses
- State management rules apply to ALL solutions (BLoC, Riverpod, GetX, MobX, Signals)
- Full checklist in [CHECKLIST.md](./CHECKLIST.md)
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.