Skip to content

feat: add argument-hint + $ARGUMENTS to sdk-upgrade and analysis-upgrade skills #122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ryzizub merged 1 commit into from
Jul 1, 2026
Merged

feat: add argument-hint + $ARGUMENTS to sdk-upgrade and analysis-upgrade skills #122

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions skills/dart-flutter-sdk-upgrade/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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.

Expand Down
6 changes: 4 additions & 2 deletions skills/very-good-analysis-upgrade/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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
Expand Down Expand Up @@ -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'
Expand Down
Loading