very-good-analysis-upgrade

Upgrades the very_good_analysis lint package in Dart and Flutter projects with minimal lint fixes.

162|23|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/VeryGoodOpenSource/vgv-ai-flutter-plugin --skill very-good-analysis-upgrade-verygoodopensource
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: very-good-analysis-upgrade
Source: https://github.com/VeryGoodOpenSource/vgv-ai-flutter-plugin/tree/main/skills/very-good-analysis-upgrade
Command: npx skills add https://github.com/VeryGoodOpenSource/vgv-ai-flutter-plugin --skill very-good-analysis-upgrade-verygoodopensource

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Upgrading the very_good_analysis lint package often introduces new lint rules that break builds, and developers struggle to keep the change scoped to a clean, reviewable PR without unrelated refactors or forced dependency resolution. ## Core Features & Use Cases - Guided version bump: Updates the very_good_analysis entry in pubspec.yaml with the VGV caret convention, resolving the target version from arguments or the pub.dev API. - Scoped lint fixes: Runs flutter analyze or dart analyze, fixes only warnings introduced by the new rules, and flags behavior-risky fixes like avoid_dynamic_calls casts for human review. - Conflict handling and PR creation: Reports pub solver conflicts by naming both constraints instead of forcing resolution, then stages only the changed files into a focused lint-compliance PR. - Use Case: In a monorepo, bump very_good_analysis to 10.0.0 across every sub-package's pubspec, run one root-level analyze pass, fix the new warnings, and open a clean PR. ## Quick Start Ask the assistant to upgrade very_good_analysis to the latest version in this Flutter project and fix any new lint warnings.

Frequently Asked Questions about very-good-analysis-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade very_good_analysis in a Flutter project?

Update the very_good_analysis entry under dev_dependencies in pubspec.yaml to the target version with a caret prefix, run flutter pub get, then flutter analyze. Fix only the new warnings introduced by the bump and commit the changes as a focused PR.

How do I handle lint warnings after a very_good_analysis upgrade?

Run flutter analyze or dart analyze to list warnings introduced by the new rules, then fix each minimally without refactoring. Style-only rules like prefer_const_constructors are safe to fix; behavior-risky ones like avoid_dynamic_calls should be flagged for human review.

Should very_good_analysis be pinned exactly or use a caret constraint?

Use the caret constraint, such as very_good_analysis: ^10.0.0, which is the VGV convention. A caret lets lint patch releases land without a PR, while an exact pin turns every patch release into its own pull request.

What happens when flutter pub get fails after a very_good_analysis bump?

Read the solver output and report the conflict by naming both constraints, such as build_runner requiring analyzer ^6.4.1 versus very_good_analysis requiring analyzer ^7.0.0. Do not force resolution, loosen other dependencies, or run pub upgrade --major-versions.

Does a very_good_analysis upgrade work in a monorepo?

Yes, but each sub-package's pubspec.yaml needs its own version bump, and pub get must run inside each package. Run analyze once from the repository root to surface every package's new warnings in a single pass.