flutter-dart-code-review
by affaan-mflutter-dart-code-review is a library-agnostic Flutter and Dart code review checklist for architecture, widget quality, state management, performance, accessibility, security, and clean code. Use it as a structured flutter-dart-code-review guide for Code Review across BLoC, Riverpod, Provider, GetX, MobX, Signals, or custom patterns.
This skill scores 74/100 and is worth listing: it provides a substantial, library-agnostic Flutter/Dart review checklist that can help an agent perform code review with less guesswork than a generic prompt. For directory users, that means a credible install candidate with real review value, though the repo still lacks some adoption aids that would make triggering and reuse even easier.
- Substantial review workflow content: the SKILL.md body is large, with 17 H2 sections and 45 H3 subsections covering project health, Dart pitfalls, performance, accessibility, security, and architecture.
- Library-agnostic scope increases reuse across Flutter stacks, explicitly covering BLoC, Riverpod, Provider, GetX, MobX, and Signals.
- The skill includes concrete checklist-style guidance and repo/file references, which improves agent triggerability and makes it easier to execute a review consistently.
- No install command, support files, or companion references are provided, so users must rely on SKILL.md alone to understand how to use it.
- The file contains placeholder markers and no separate examples/tests, which slightly reduces trustworthiness and progressive disclosure quality.
Overview of flutter-dart-code-review skill
What flutter-dart-code-review does
The flutter-dart-code-review skill is a practical review checklist for Flutter and Dart codebases. It helps you inspect apps for architecture, widget quality, state management mistakes, Dart language pitfalls, performance issues, accessibility gaps, and security concerns without assuming a specific package stack.
Who it is for
Use the flutter-dart-code-review skill if you review Flutter apps, maintain a shared codebase, or want a structured second pass before merging. It is most useful for engineers who need consistent review criteria across BLoC, Riverpod, Provider, GetX, MobX, Signals, or custom patterns.
When it adds real value
This skill is strongest when you need a repeatable flutter-dart-code-review for Code Review workflow, not a generic “looks good” prompt. It is designed to catch issues that are easy to miss in fast reviews: business logic in widgets, loose typing, weak lint settings, stale generated files, and architecture drift.
How to Use flutter-dart-code-review skill
Install and load it correctly
Use the flutter-dart-code-review install flow from your skill manager, then point your agent at the repository and ask for a code review using the skill. The exact install command depends on your environment, but the skill path is skills/flutter-dart-code-review, and the repo source is affaan-m/everything-claude-code.
Start with the right files
Read SKILL.md first because it contains the review checklist. Then inspect any repository docs or config files that shape review standards in your codebase, especially analysis_options.yaml, pubspec.yaml, generated-code files, and architecture folders such as lib/, test/, features/, or core/.
Give the skill review-ready input
A strong flutter-dart-code-review usage prompt names the app slice, the review goal, and the constraints. For example: “Review this Flutter feature for architecture, widget purity, null-safety issues, and performance regressions. Focus on files in lib/features/cart/ and flag anything that would block merge.” That gives the skill a bounded target instead of a vague request.
Use a focused review workflow
For best results, run the skill in two passes: first a broad scan for high-risk problems, then a narrower pass on the flagged files. The broad pass should check structure, state flow, and lint hygiene; the second pass should verify the exact lines, side effects, and edge cases that matter before approval.
flutter-dart-code-review skill FAQ
Is flutter-dart-code-review only for one state management library?
No. The skill is intentionally library-agnostic, so it works across common Flutter patterns and custom architectures. That makes it a better fit than a package-specific prompt when your team does not standardize on one state solution.
Is it beginner-friendly?
Yes, if you want a checklist-driven review guide rather than deep framework theory. It is less useful if you need tutorial-style explanations, because the flutter-dart-code-review skill is aimed at evaluation and decision support.
When should I not use it?
Skip it if you only need a quick style check or if your task is outside Flutter/Dart. It is also not the best choice when you need automated linting or test execution; it supports human review, not CI replacement.
How to Improve flutter-dart-code-review skill
Give sharper context than “review this code”
The best flutter-dart-code-review guide inputs include the feature name, app layer, risk area, and desired depth. Compare “review my Flutter app” with “review the checkout flow for widget purity, async error handling, and unnecessary rebuilds.” The second prompt produces more relevant findings because it tells the skill what matters.
Share constraints and architecture intent
If your codebase uses feature-first structure, strict lint rules, or a specific state management approach, say so up front. The skill is designed to be framework-neutral, but it performs better when you describe the conventions it should respect instead of forcing it to infer them.
Iterate on the first review
After the first pass, ask follow-ups that target the highest-risk findings: “show only merge-blocking issues,” “recheck state access in these widgets,” or “separate correctness problems from maintainability concerns.” That reduces noise and turns flutter-dart-code-review into a more actionable review loop.