When to use / when NOT to use
- Use before cutting a release branch/tag.
- Do not use for day-to-day dependency updates.
Preconditions (tools, versions, repo state)
- Flutter toolchain installed.
pubspec.yamlin repo root.- Clean working tree for
--execute.
Workflow (DISCOVER → PLAN → EXECUTE → VERIFY → REPORT)
- DISCOVER: detect Flutter project and release metadata files.
- PLAN: build pre-release checklist.
- EXECUTE: enforce clean state and prepare checks.
- VERIFY: run analyze/test/build smoke commands.
- REPORT: summarize go/no-go outcomes.
Exact commands and expected signals
skills/flutter-release-readiness/scripts/run.sh --dry-run
skills/flutter-release-readiness/scripts/run.sh --verify-only --ci
skills/flutter-release-readiness/scripts/run.sh --execute --ci
Success: report generated and verification checks complete. Failure: missing toolchain/project or failing checks.
If it fails (checklist)
- Run
flutter doctorand fix setup. - Resolve analyze/test failures before release.
- Re-run with
--verbose.
Final report template
- Release scope and version/changelog status.
- Verification command outcomes.
- Blocking issues.
- Next actions and rollback command.