flutter/flutter-intellij · Archived

verify-eap-compatibility

Ensure the plugin remains compatible with the latest IntelliJ Platform releases and EAP (Early Access Program) builds.

First seen Jul 20, 2026

Installation

$ npx skills add flutter/flutter-intellij --skill verify-eap-compatibility

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

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

Also in this package

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

npx skills add flutter/flutter-intellij

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 1,695 B
  • docs SUMMARY.md 150 B

History

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

SKILL.md

Skill: Plugin Compatibility & EAP Verification

You are tasked with ensuring the plugin remains compatible with the latest IntelliJ Platform releases and EAP (Early Access Program) builds.

Objective

Ensure the plugin remains compatible with the latest IntelliJ Platform releases and EAP (Early Access Program) builds.

Workflow Instructions

1. Target EAP

  • Temporarily update gradle.properties to target the latest IntelliJ Platform EAP version.

2. Run Verification

  • Run ./gradlew testClasses to ensure the project compiles against the EAP.
  • Execute ./gradlew verifyPlugin to check for binary incompatibilities or broken API usages in the new version.
  • Run ./gradlew test to check for functional regressions with the EAP.

3. Check Bounds

  • Review plugin.xml for <idea-version since-build="..." until-build="..."/>. Ensure until-build is open-ended or appropriately set for the new version.

4. Resolve Issues

  • Fix any compilation errors or verification warnings specific to the new platform version.

5. Report & Review

  • Summarize any required changes or blockers for supporting the new version.
  • 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 compatibility fixes closely.
  • Do not commit or push.
  • Provide a suggested Git commit message (e.g., "Fix EAP compatibility: Resolve invalid until-build").