What problem does it solve? Dart and Flutter projects accumulate lint violations, type errors, and outdated API usages that are tedious to find and fix manually. This Skill runs static analysis to surface warnings and errors, then applies automated fixes so code stays clean before commits. ## Core Features & Use Cases - Static Analysis Execution: Run dart analyze on a project or target directory to identify type errors, style violations, and potential runtime bugs, with optional --fatal-infos for strict CI gating. - Automated Fixes: Preview changes with dart fix --dry-run and apply them with dart fix --apply, then format results with dart format. - Analyzer Configuration: Set up analysis_options.yaml with strict type checks (strict-casts, strict-inference, strict-raw-types), linter rules, formatter settings, and diagnostic suppression patterns. - Use Case: Before committing a Flutter feature branch, run the analysis workflow to catch an implicit downcast error, apply automated fixes for deprecated API usages, and verify zero remaining diagnostics. ## Quick Start Run dart analyze on my project and apply any available automated fixes, then format the changed files.