Download for MacApple silicon, macOS 14+
Skill

dart-flutter-sdk-upgrade

@verygoodopensource Updated 2026-10-20

VGV-specific reference for bumping Dart and Flutter SDK constraints across packages, covering pubspec.yaml environment constraints, CI workflow Flutter versions, and SDK upgrade PR preparation. Use it when upgrading the Flutter or Dart SDK version in any VGV repository, on phrases like "bump Flutter to 3.x", "update SDK constraints", "upgrade Dart SDK", "update CI Flutter version", "bump SDK version", or "prep the SDK upgrade PR", and also when a bump is already underway and something breaks: "pub get fails after I changed the environment block", "version solving failed after bumping the SDK", "a dependency requires an older SDK", "get me unblocked on the Flutter upgrade", or "which Dart version ships with Flutter 3.x". It owns the whole bump, including the conflicts it surfaces, even when the blocking package has a skill of its own.

a11yaibest-practicesblocclaude-codedartflutteri18n

Install

With your agent

Install OMGSkills skill "verygoodopensource/vgv-ai-flutter-plugin:skills/dart-flutter-sdk-upgrade" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/VeryGoodOpenSource/vgv-ai-flutter-plugin /tmp/vgv-ai-flutter-plugin && ln -s /tmp/vgv-ai-flutter-plugin/skills/dart-flutter-sdk-upgrade ~/.claude/skills/dart-flutter-sdk-upgrade

From README

VGV Flutter/Dart SDK Upgrade — Quick Reference One PR per project. Only CI workflow and pubspec.yaml changes — no logic, no dependency version bumps, no test changes. --- Core Standards Apply these standards to all SDK upgrade work: Flutter and Dart versions differ — a Flutter release ships a Dart SDK whose version number is unrelated to it, and the pubspec sdk: constraint takes the Dart number, never the Flutter one. Look the pairing up in the release archive at Never state a bundled Dart version from memory — not from recall, not by inference from the Flutter number, and not from an example in this file. Either the user supplied the Dart version, or you read it off the archive, or you ask.