| name | flutter-updater |
| description | Specialized skill for updating Flutter/Dart packages, adhering to the standards defined in project-updater. Use when this capability is needed. |
| metadata | {"author":"bramp"} |
Flutter Package Updater
This skill specializes in updating Flutter/Dart packages, adhering to the standard philosophy in project-updater/SKILL.md.
Language Standards
- Workspaces: Adopt Dart/Flutter workspaces (requires SDK ^3.5.0) for multi-package projects.
- Migration from Melos: If migrating from Melos:
- Add
workspace and resolution: workspace to pubspec.yaml.
- Create a
Makefile that replicates all Melos scripts.
- Remove
melos.yaml and melos from dev_dependencies.
- Linting: Prefer
package:very_good_analysis for the strictest modern linting rules.
- Formatting: Always use
dart format.
- Pub.dev Standards: Ensure
CHANGELOG.md is updated and publish_to is commented out (to prevent accidental local publishing while still signaling intent).
Standard Makefile (Flutter)
A Makefile for a Flutter project should implement the standard targets:
all: format analyze test
format: dart format .
analyze: dart analyze
test: dart test (or flutter test)
test-ci: dart test --reporter=compact
fix: dart fix --apply
upgrade: dart pub upgrade --major-versions --tighten
GitHub Actions (Flutter)
The test.yml for Flutter should:
- Use
subosito/flutter-action@v2.
- Cache the
.pub-cache.
- Run
make test-ci.
Also ensure .github/dependabot.yml is present to keep dependencies updated, including the standard cooldown settings:
cooldown:
default-days: 7
semver-major-days: 30
semver-minor-days: 14
semver-patch-days: 3
Dependency Management
- Use
dart pub outdated to identify major version upgrades.
- Tighten SDK constraints to the latest stable release.
Source: bramp/updater — distributed by TomeVault.