SkillsAdd

flutter/flutter-intellij · Archived

resolve-verification-issues

Eliminate plugin verification warnings and errors (Internal API usage, Override-only API usage, etc.) identified by ./gradlew verifyPlugin.

First seen Jul 20, 2026

Installation

$ npx skills add flutter/flutter-intellij --skill resolve-verification-issues
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

cleanup-code-inspections Same source · more installs
flutter/flutter-intellij

Reduce technical debt and improve code quality by systematically resolving static analysis warn…

8 installs
code-review Same source · more installs
flutter/flutter-intellij

Perform a pedantic, multi-perspective code review on the current diff or git changes against th…

8 installs
audit-ui-thread-safety Same source · more installs
flutter/flutter-intellij

Prevent UI freezes and ensure a responsive user experience by validating threading rules and mi…

7 installs
audit-dependencies Same source · more installs
flutter/flutter-intellij

Optimize plugin size and security by removing unused dependencies and updating outdated librari…

7 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

connect-required-verification-information Similar name
stripe/ai

>- Use this skill when the user asks what information a Stripe Connect connected account must p…

25 installs
verification-before-completion Similar name
obra/superpowers

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs …

203.7K installs
extension-email-verification Similar name
caffeinelabs/skills

Support for sending an email with a link the recipient can click to prove they own the email ad…

18.5K installs
verification-loop Similar name
affaan-m/ecc

A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code …

9.1K installs
django-verification Similar name
affaan-m/ecc

Verification loop for Django projects: migrations, linting, tests with coverage, security scans…

8.8K installs
springboot-verification Similar name
affaan-m/ecc

Verification loop for Spring Boot projects: build, static analysis, tests with coverage, securi…

8.7K installs

Also in this package

Other skills from flutter/flutter-intellij · top by installs.

npx skills add flutter/flutter-intellij
cleanup-code-inspections 8 code-review 8 audit-ui-thread-safety 7 audit-dependencies 7 audit-accessibility 7 migrate-intellij-util 6 verify-eap-compatibility 6 remove-platform-version 6 cleanup-unused-assets 6 add-missing-unit-test 6

Browse all from flutter/flutter-intellij

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2.0K
License LICENSE
Default branch main
Open issues 647
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,098 B
  • docs SUMMARY.md 174 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 6 installs

SKILL.md

Skill: Resolve Plugin Verification Issues

You are tasked with eliminating plugin verification warnings and errors (Internal API usage, Override-only API usage, etc.).

Objective

Eliminate plugin verification warnings and errors (Internal API usage, Override-only API usage, etc.).

Workflow Instructions

1. Baseline

  • Run ./gradlew testClasses to ensure project compiles.
  • Run ./gradlew test and ./gradlew verifyPlugin to establish a clean baseline.

2. Analyze Report

  • Identify distinct issues to resolve (e.g., "Override-only API usage in ClassX").

3. Implement Fix

  • Resolve the specific issue in the current branch.
  • Ensure the fix is minimal and targeted.

4. Verify Fix

  • Run ./gradlew testClasses to ensure no new compilation errors.
  • Run ./gradlew verifyPlugin again to confirm the specific warning is gone and quantify the improvement.
  • Run ./gradlew test to ensure no regressions.

5. Validation & Manual Testing

  • Explain how to verify the fix manually by running ./gradlew runIde.
  • Provide specific navigation steps for the user to reach the changed code within the plugin (e.g. "Open Settings > Languages & Frameworks > Flutter...").
  • Verify that the changes do not introduce runtime errors or regressions.

6. Report & Review

  • Summarize the remaining verifyPlugin issues (e.g., "Total remaining issues: X compatibility warnings, Y internal API usages").
  • Confirm that ./gradlew runIde validation passed.
  • Test Location: Explicitly state where in the IDE the user should go to test the changed functionality (e.g., "Go to Preferences > Languages & Frameworks > Flutter").
  • Action: Ask the user to review the fix closely.
  • Do not commit or push.
  • Provide a suggested Git commit message including specific counts (e.g., "Fix Internal API usage in ClassX: 5 experimental APIs used -> 4 experimental APIs used").