flutter-review

Flutter review

A review is worth running when a second reader would catch what the author cannot. That is the whole design here: the reading happens in a subagent with its own context, which never saw the conversation that produced the code, so it cannot inherit the author's assumptions about what the code does.

You orchestrate. You resolve what to review, spawn the reviewer, check its work, and carry the fixes. You do not do the reviewing yourself: reviewing your own recent edits in the same context is the failure this skill exists to avoid.

1. Resolve the scope

Take the first branch that applies:

1. Arguments name paths or globs (lib/features/monitor/**, two file paths, a feature name that maps to a directory): that is the scope.
2. git status --porcelain shows uncommitted changes: those files are the scope. This is the common case, and it is what "review my work" means while the work is in progress.
3. The branch is ahead of its upstream or the default branch: git diff --name-only $(git merge-base HEAD @{u} 2>/dev/null || git merge-base HEAD main)...HEAD is the scope.
4. Nothing resolves: ask what to review. Do not review the whole lib/ tree on a guess; on a real app that produces a long report nobody reads.

Filter the resolved list to Dart sources. Drop generated files (*.g.dart, *.freezed.dart, _previews.g.dart), and say how many you dropped.

Confirm the project is on this stack before spawning anything: pubspec.yaml names magic or fluttersdk_wind. If it names neither, say so and stop; the rulebooks this review applies would be inventing rules for a project that never adopted them.

Success criterion: a concrete list of Dart files, shown to the user with its origin ("12 uncommitted files", "8 files ahead of main").

2. Pick the reviewer

Reviewer	When
fluttersdk:flutter-reviewer	The default. A fix, a screen, a handful of files inside one layer.
fluttersdk:flutter-reviewer-deep	The change crosses layers (controller plus view plus model, or route plus middleware plus authorization), introduces a pattern the app will copy, or is a whole new feature or module. Also when a standard review came back clean and the user still thinks something is off.