flutter-dart-code-review

Identify Flutter/Dart code-review gaps in widget usage and state management.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/richardnpaul/everything-vscode-copilot --skill flutter-dart-code-review-richardnpaul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flutter-dart-code-review
Source: https://github.com/richardnpaul/everything-vscode-copilot/tree/main/.github/skills/flutter-dart-code-review
Command: npx skills add https://github.com/richardnpaul/everything-vscode-copilot --skill flutter-dart-code-review-richardnpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flutter and Dart projects often suffer from widget bloat, inconsistent state-management practices, and fragile architectures that hinder maintainability, testability, and performance. This library-agnostic checklist provides a comprehensive guide to enforce quality across UI, business logic, data layers, and architectural boundaries.

Core Features & Use Cases

  • Widget decomposition and separation of concerns: guidance to keep widgets purely presentational and extract reusable components.
  • State management discipline: recommendations for BLoC, Riverpod, Provider, GetX, MobX, and Signals with proper dependencies and immutability.
  • Quality gates for performance, accessibility, and security: checks to prevent anti-patterns, ensure accessibility, and guard against common security pitfalls.
  • Clean architecture and testability: guidance on layering, dependency inversion, and testability considerations.

Quick Start

Run this checklist against a Flutter/Dart project to surface widget, state-management, performance, accessibility, and security issues.

Frequently Asked Questions about flutter-dart-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a Flutter code review to check widget bloat and state management?

Run this structured checklist against your Flutter project to identify widget decomposition gaps and enforce state management discipline across BLoC, Riverpod, Provider, GetX, MobX, or Signals patterns.

What is the best way to review Flutter code for clean architecture and testability?

The best way to review Flutter code for clean architecture is using a library-agnostic checklist that enforces UI separation of concerns, dependency inversion, and layering to ensure robust testability.

Can I use this Dart code review checklist for apps using Riverpod or GetX?

Yes, this Dart code review checklist is library-agnostic and explicitly supports reviewing state management dependencies and immutability for apps using Riverpod, GetX, BLoC, Provider, MobX, or Signals.

How does this checklist handle Flutter performance and accessibility checks?

This checklist handles Flutter performance and accessibility by applying quality gates that prevent anti-patterns, enforce accessibility compliance, and guard against common security pitfalls in your widgets.

Why should I use a library-agnostic checklist for Dart code review?

A library-agnostic checklist for Dart code review ensures consistent evaluation of immutability, lint compliance, and architectural boundaries regardless of whether your project uses BLoC, Riverpod, or GetX.

Does this Flutter code review enforce separation of concerns in widgets?

Yes, this Flutter code review enforces separation of concerns by providing guidance to keep widgets purely presentational and extracting reusable components to prevent widget bloat.