flutter-perf-audit

Automate a Flutter performance audit by scanning build methods, unnecessary rebuilds, and non-const widgets to identify jank sources. The audit outputs a structured performance report under docs/reviews for the affected module.

Unnecessary rebuilds in Flutter are often caused by non-const widgets and overly wide local scopes. Scanning source code build methods identifies these performance bottlenecks and reports them in a structured markdown file.

Check Flutter projects for missing const widgets and large build methods using an automated source code scan. It identifies deep nesting, long files, and long lists, generating a structured performance report for code reviews.

You can integrate the Flutter performance report into your code review workflow by saving the output under docs/reviews. This allows teams to track and reference performance issues during major screen refactors or regular reviews.

Run a Flutter performance audit after major screen refactors, during performance review stages, or when investigating UI jank and frame drops. It helps quickly locate common performance issues like deep nesting and long lists.

The best way to identify long lists and deep nesting is by scanning Flutter source code for common UI performance issues. This process generates a structured performance report detailing the affected modules.