From 66f2ad89e6aa2930248191e3a80f9fb662c29922 Mon Sep 17 00:00:00 2001 From: Dominik Simonik Date: Wed, 1 Jul 2026 16:28:13 +0200 Subject: [PATCH] feat: add argument-hint + $ARGUMENTS to sdk-upgrade and analysis-upgrade skills Both skills now declare an argument-hint in frontmatter and consume $ARGUMENTS in the body so an invoked version is used as the target: - dart-flutter-sdk-upgrade: hint "[flutter-version]"; $ARGUMENTS drives the target Flutter/Dart version resolution in step 0. - very-good-analysis-upgrade: hint "[version]"; $ARGUMENTS drives the target very_good_analysis version, falling back to the pub.dev latest. Closes #113 Co-Authored-By: Claude Opus 4.8 --- skills/dart-flutter-sdk-upgrade/SKILL.md | 8 +++++--- skills/very-good-analysis-upgrade/SKILL.md | 6 ++++-- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/skills/dart-flutter-sdk-upgrade/SKILL.md b/skills/dart-flutter-sdk-upgrade/SKILL.md index 008e15e..8f41d8b 100644 --- a/skills/dart-flutter-sdk-upgrade/SKILL.md +++ b/skills/dart-flutter-sdk-upgrade/SKILL.md @@ -9,6 +9,7 @@ when_to_use: > Use when upgrading the Flutter or Dart SDK version in any VGV repository. Trigger 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". +argument-hint: "[flutter-version]" allowed-tools: Read Glob Grep Edit Write Bash model: sonnet effort: medium @@ -46,9 +47,10 @@ for the target Flutter release before editing any files. 2. Find the target Flutter stable release 3. Note the Dart version listed alongside it -If the user has not specified a Flutter version, look up the latest Flutter stable release -from that same page. For pure Dart packages (no Flutter dependency), the Dart version is -whatever the user specifies or the latest stable — no Flutter mapping needed. +The target version comes from `$ARGUMENTS` (e.g. `3.41.0`) when the user supplied one. If +`$ARGUMENTS` is empty, look up the latest Flutter stable release from that same page. For pure +Dart packages (no Flutter dependency), the Dart version is whatever `$ARGUMENTS` specifies or +the latest stable — no Flutter mapping needed. Confirm both resolved versions with the user before editing files. diff --git a/skills/very-good-analysis-upgrade/SKILL.md b/skills/very-good-analysis-upgrade/SKILL.md index 2648515..fe95178 100644 --- a/skills/very-good-analysis-upgrade/SKILL.md +++ b/skills/very-good-analysis-upgrade/SKILL.md @@ -1,6 +1,7 @@ --- name: very-good-analysis-upgrade description: Upgrade very_good_analysis lint package to new version across Dart/Flutter projects. Handles version bump, lint fixes, and PR creation. +argument-hint: "[version]" allowed-tools: Read Glob Grep Bash model: sonnet effort: medium @@ -29,8 +30,9 @@ These standards apply to every `very_good_analysis` upgrade. Confirm two things before proceeding: -1. **Target version** — if the user didn't specify a version, fetch the latest from the pub.dev API - and use that. Don't ask — just look it up and proceed: +1. **Target version** — use `$ARGUMENTS` as the target version when the user supplied one + (e.g. `10.0.0`). If `$ARGUMENTS` is empty, fetch the latest from the pub.dev API and use + that. Don't ask — just look it up and proceed: ```bash curl -s https://pub.dev/api/packages/very_good_analysis | jq -r '.latest.version'