flutter-code-review
Skill4 starsChanged 3 months agoMITView on GitHub
Use when reviewing Flutter code for correctness, architecture compliance, design system usage, linting, or testing coverage. Also use before merging a PR or when the user asks for a code review of Dart or Flutter files.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- thienqo/flutter-skillstheir own version, first seen Nov 1, 2026
- thiennc-tesoglobal/flutter-skillstheir own version, first seen Aug 30, 2026
- Piinks/flutter-skillstheir own version, first seen Mar 6, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- thiennc-tesoglobal/flutter-skills★ 16same name
- thienqo/flutter-skills★ 16same name
- Piinks/flutter-skills★ 9same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-annotationsSkill
- android-accessibility-validatorSkill
- android-compose-architecture-reviewSkill
- android-kotlin-api-design-reviewerSkill
- android-performance-profilerSkill
- flutter-accessibility-validatorSkill
- flutter-bug-investigationSkill
- flutter-design-architectureSkill
- flutter-feature-analysisSkill
- flutter-feature-implementationSkill
- flutter-performance-optimizerSkill
- ios-accessibility-validatorSkill
- ios-performance-profilerSkill
- ios-swift-api-design-reviewerSkill
- ios-swiftui-architecture-reviewSkill
- shared-bug-investigationSkill
- shared-perf-comparison-videoSkill
- shared-product-motion-videoSkill
- shared-task-workflowSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 64
🔴 Blocker: Must fix (functionality, security, linting)
- Distinctive: line 65
🟠 Major: Should fix (performance, architecture, design system)
- Very specific: line 70
Check file structure (data/domain/view)
- Distinctive: line 71
Verify design system usage
- Distinctive: line 72
Check state management (@injectable)
- Distinctive: line 74
Check tests (suggest improvements)
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Code Review Skill
7 Criteria
1. Functionality (🔴 Blocker)
- Logic errors, missing error handling, null safety violations
2. Readability (🟠 Major)
- Clear naming, proper comments, no dead code
3. Optimization (🟠 Major)
- Unnecessary rebuilds, N+1 queries, missing const
4. Architecture (🟠 Major)
- data/domain/view pattern, repository pattern, @injectable DI
5. Design System (🟠 Major)
- ColorPalette, Spacing, Project Design System Widgets (no hardcoded)
6. Linting (🔴 Blocker)
flutter analyzemust pass (zero errors)
7. Testing (Optional)
- 90%+ unit, 50%+ widget coverage (suggest, don't block)
Quick Checks
// ❌ Hardcoded color
Text('Hi', style: TextStyle(color: Colors.red))
// ✅ Use ColorPalette
Text('Hi', style: TextStyle(
color: ColorPalette.coloursBasicText.platformBrightnessColor(context),
))
// ❌ Business logic in widget
final total = items.fold(0, (s, i) => s + i.price);
// ✅ Logic in Bloc/Cubit
@injectable class MyBloc { ... }
// ❌ No error handling
Future<Data> fetch() async {
return await api.call();
}
// ✅ Try-catch
Future<Data> fetch() async {
try {
return await api.call();
} catch (e) {
throw NetworkException(e.toString());
}
}Severity
- 🔴 Blocker: Must fix (functionality, security, linting)
- 🟠 Major: Should fix (performance, architecture, design system)
- 🟢 Minor: Nice to fix (naming, comments)
Process
flutter analyze(must pass)- Check file structure (data/domain/view)
- Verify design system usage
- Check state management (@injectable)
- Verify error handling
- Check tests (suggest improvements)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

