What problem does it solve?
IntelliJ plugin codebases often use standard Java collections and string utilities that waste memory and diverge from platform conventions. This Skill guides incremental, verified migration of standard Java/Kotlin classes to IntelliJ's specialized com.intellij.util implementations.
Core Features & Use Cases
- API Migration Mapping: Replaces ArrayList with SmartList, HashMap with ContainerUtil maps, string operations with StringUtil, javax.swing.Timer with Alarm, and null checks with ObjectUtils.
- Safe Incremental Workflow: Limits each change to a single package and a maximum of 50 lines, with baseline and post-migration verification via ./gradlew testClasses, test, and verifyPlugin.
- Review-Ready Reporting: Produces a migration summary, manual test steps with exact IDE navigation paths, and a suggested Git commit message without committing automatically.
- Use Case: A Flutter IntelliJ plugin maintainer wants to reduce memory overhead by converting HashMap usages in one package to ContainerUtil maps while confirming no test regressions.
Quick Start
Ask the assistant to migrate one standard Java collection usage in a single package to its com.intellij.util equivalent and verify the build with Gradle tests.