# Flutter Deps Upgrade

> Upgrade Dart/Flutter package dependencies using `pub outdated/upgrade` with deterministic verification gates and migration-aware reporting.

- Skill: `nickcuypers/flutter-deps-upgrade` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add nickcuypers/flutter-deps-upgrade`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nickcuypers/flutter-deps-upgrade/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: nickcuypers (https://skillmd.com/u/nickcuypers)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/nickcuypers/flutter-deps-upgrade

---


## When to use / when NOT to use
- Use for package dependency hygiene in Flutter apps/packages.
- Do not use for SDK channel/version upgrades.

## Preconditions (tools, versions, repo state)
- Flutter/Dart installed.
- `pubspec.yaml` present.
- Clean git state before execute.

## Workflow (DISCOVER → PLAN → EXECUTE → VERIFY → REPORT)
1. DISCOVER: detect Flutter setup and monorepo indicators.
2. PLAN: inspect outdated graph and major-version risk.
3. EXECUTE: run `flutter pub upgrade`.
4. VERIFY: run `pub outdated`, format check, analyze, test.
5. REPORT: summarize package risk and follow-up actions.

## Exact commands and expected signals
```bash
skills/flutter-deps-upgrade/scripts/run.sh --dry-run
skills/flutter-deps-upgrade/scripts/run.sh --execute --ci
skills/flutter-deps-upgrade/scripts/run.sh --verify-only --ci
```
Success: outdated inventory and verification outputs available.
Failure: missing Flutter project/toolchain or analysis/test breakages.

## If it fails (checklist)
- Validate SDK constraints and lockfile state.
- Re-run with `--verbose` to isolate failing package.
- Use staged upgrades for major packages.

## Final report template
- Current dependency posture (outdated summary).
- Upgrades applied (if execute).
- Analyze/test status.
- Breaking packages and migration notes.
- Rollback command.