Flutter Fix And Verify

When to use / when NOT to use

• Use in daily dev loops before commit/PR push.
• Do not use as a substitute for release-specific checks.

Preconditions (tools, versions, repo state)

• Flutter/Dart installed.
• pubspec.yaml present.
• Clean tree for --execute.

Workflow (DISCOVER → PLAN → EXECUTE → VERIFY → REPORT)

1. DISCOVER: validate toolchain/project.
2. PLAN: determine fix/check sequence.
3. EXECUTE: apply fixes and formatting in execute mode.
4. VERIFY: run analyze + tests.
5. REPORT: summarize pass/fail and changed files.

Exact commands and expected signals

skills/flutter-fix-and-verify/scripts/run.sh --dry-run
skills/flutter-fix-and-verify/scripts/run.sh --verify-only --ci
skills/flutter-fix-and-verify/scripts/run.sh --execute

Success: analyze/tests run and report generated. Failure: missing toolchain/project or failing analyzer/tests.

If it fails (checklist)

• Run flutter doctor.
• Address analyzer/test failures from report output.
• Re-run in verify-only to confirm clean status.

Final report template

• Fixes applied (if any).
• Analyze/test outcomes.
• Remaining blockers.
• Next actions.