very-good-analysis-upgrade

Featured

Upgrade the very_good_analysis lint package to a new version in any Dart or Flutter package, handling the pubspec.yaml version bump, the lint fixes the new rules force, and the PR. Trigger on phrases like "bump very_good_analysis to 10.0.0", "upgrade very_good_analysis", "update our lint package", "we're due for a lint upgrade", "take very_good_analysis to the latest", or a `dart pub get` conflict reported after a very_good_analysis bump. Use it even when the user only describes the package instead of pointing at it, because the decisions it governs are scope calls that do not need the files on disk: which constraint to write, which warnings to fix, and what stays out of the PR. The trigger is a very_good_analysis version change. A conflict surfaced by a Dart or Flutter SDK bump belongs to dart-flutter-sdk- upgrade instead, even when very_good_analysis is the package blocking resolution.

Data & Documents 161 stars 22 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
74
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Upgrade very_good_analysis This skill guides the full upgrade of `very_good_analysis` in a Dart or Flutter project. The goal is a clean, focused PR: nothing more than the version bump in `pubspec.yaml` plus the minimal code changes needed to satisfy any new lint rules introduced in that version. --- ## Core Standards These standards apply to every `very_good_analysis` upgrade. - **Keep the caret** — write `very_good_analysis: ^x.y.z`, never a bare `x.y.z`. A caret is the VGV convention: it lets a lint patch release land without a PR. "Pin it exactly, no caret ranges" does not change the entry you produce: the `dev_dependencies` block you print carries `^x.y.z`, with the reason stated in a line next to it. Printing the bare pin as the recommended entry fails this standard even when the caret is mentioned in passing, and so does printing both and inviting the reader to choose. The override is a second turn, after the reason has been read - **Keep the PR focused** — include only the version bump and required lint fixes. Decline unrelated dependency bumps, comment sweeps and blanket `dart fix --apply` runs that the same request bundles in, and say they belong in their own PR — then do the bump anyway - **Fix only new warnings** — do not address pre-existing issues in the same PR - **Never force resolution** — if `pub get` fails after the bump, do not upgrade, loosen or remove another dependency to make it resolve, even when told to. Name both conflicting ...

Details

Author
VeryGoodOpenSource
Repository
VeryGoodOpenSource/vgv-ai-flutter-plugin
Created
6 months ago
Last Updated
yesterday
Language
Shell
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

dart-flutter-sdk-upgrade

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.

161 Updated yesterday
VeryGoodOpenSource
AI & Automation Listed

flutter-dependency-upgrades

Plan, execute, or review Flutter and Dart SDK upgrades, dependency resolution, lockfile changes, package breaking changes, and compatible native toolchain migrations. Use when versions or compatibility are the task; route ordinary Dart refactoring to dart-language, security audits to flutter-security, and release artifacts to flutter-build-release.

7 Updated today
thiennc-tesoglobal
Code & Development Listed

lint-and-style-config

Enforces a strict analysis_options.yaml built on very_good_analysis with strict-casts/strict-raw-types, a fixed set of silence-producing bug classes promoted to error (unawaited_futures, discarded_futures, empty_catches, use_build_context_synchronously, cancel_subscriptions, close_sinks, avoid_dynamic_calls, exhaustive_cases, avoid_print), dart format as the sole whitespace authority, generated-file excludes mirrored to coverage, and line-scoped-only suppression discipline; teaches the version-pinned-include trap (a missing include silently disables all rules), the errors-only-re-ranks-vs-linter-enables mechanic, and the sealed-switch analyze-vs-compile gap. Use when editing analysis_options.yaml, adding or disabling a lint, writing an `// ignore:`/`// ignore_for_file:`, bumping the Dart SDK or very_good_analysis version, wiring riverpod_lint, or explaining why discarded_futures, use_build_context_synchronously, close_sinks, or missing_provider_scope fires.

0 Updated 1 months ago
zakariaf