resolve-verification-issues

Eliminate IntelliJ plugin verification warnings and errors reported by Gradle verifyPlugin.

2.0k|355|Updated Jul 25, 2016
One-click install
npx skills add https://github.com/flutter/flutter-intellij --skill resolve-verification-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-verification-issues
Source: https://github.com/flutter/flutter-intellij/tree/main/.agents/skills/resolve-verification-issues
Command: npx skills add https://github.com/flutter/flutter-intellij --skill resolve-verification-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Gradle verifyPlugin task flags Internal API usage, Override-only API usage, and other compatibility warnings in the Flutter IntelliJ plugin, and resolving them manually requires careful, incremental fixes with repeated verification.

Core Features & Use Cases

  • Baseline Establishment: Runs testClasses, test, and verifyPlugin to confirm a clean starting point before making changes.
  • Targeted Fixes: Identifies distinct verification issues and applies minimal, focused code changes to resolve each one.
  • Verification Loop: Re-runs compilation, tests, and verifyPlugin to confirm warnings are gone and no regressions were introduced.
  • Use Case: A contributor sees "Internal API usage in ClassX" in the verifyPlugin report; the Skill fixes the usage, validates it with ./gradlew runIde, and proposes a commit message quantifying the improvement.

Quick Start

Fix the Internal API usage warnings reported by ./gradlew verifyPlugin and verify the fix with tests and a manual runIde check.

Frequently Asked Questions about resolve-verification-issues

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

FAQPage Schema
How do I fix IntelliJ plugin verification warnings from verifyPlugin?▼

Run ./gradlew verifyPlugin to identify distinct issues such as Internal API usage, then apply a minimal targeted fix for each one. Re-run testClasses, test, and verifyPlugin to confirm the warning is gone and no regressions occurred.

How to resolve Internal API usage errors in an IntelliJ plugin?▼

Locate the flagged class in the verifyPlugin report and replace the internal API call with a supported public API equivalent. Verify the change compiles with ./gradlew testClasses and that the warning count decreases in the next verifyPlugin run.

Does this workflow run tests before changing plugin code?▼

Yes, the workflow establishes a baseline by running ./gradlew testClasses, ./gradlew test, and ./gradlew verifyPlugin before any fix. This ensures pre-existing failures are not confused with regressions introduced by the change.

How do I manually verify a plugin fix in the IDE?▼

Run ./gradlew runIde to launch a sandbox IDE instance with the modified plugin. Navigate to the affected feature, such as Preferences > Languages & Frameworks > Flutter, and confirm the changed behavior works without runtime errors.

Does the verification fix workflow commit changes automatically?▼

No, the workflow explicitly does not commit or push changes. It summarizes remaining verifyPlugin issues and provides a suggested commit message with specific warning counts for the user to review.