Skip to content

datit309/supergraph / plugins/supergraph/skills/flutter-dart-code-review

flutter-dart-code-review

Unverified

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.

/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 — 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
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 192kUpdated Claude CodeCodexVerifiedInstall