flutter-verification

To enforce Flutter verification before task completion, you need a mandatory gate that executes static analysis, unit testing, and build validation. This ensures code changes are validated against expected success criteria before being marked as done.

Required Flutter verification commands include standard CLI tools for static analysis, unit testing, and build validation. Running these commands confirms that no regressions were introduced and the project build remains stable.

This verification process requires the Flutter SDK and standard CLI tools to execute analysis, unit testing, and build validation. It is specifically designed for Flutter development workflows to prove code integrity and build stability.

Your pipeline lacks an automated verification gate that forces analysis, unit tests, and build commands as a prerequisite. Implementing standardized reporting ensures claims of done are backed by concrete terminal output.

You need to run build validation before submitting a pull request, marking a bug as fixed, or finalizing your work. This guarantees the Flutter project build remains stable and no regressions were introduced during development.