java-kotlin-migration-assistant

Name: java-kotlin-migration-assistant
Availability: InStock
Author: JetBrains

Translate Java code to Kotlin in Spring projects while preserving behavior and compatibility.

302|22|Updated Feb 12, 2026

Search Tags:#java #kotlin #spring #migrate #jpa #nullability #migration-strategy

Ready to run

npx skills add https://github.com/JetBrains/skills --skill java-kotlin-migration-assistant-jetbrains

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: java-kotlin-migration-assistant
Source: https://github.com/JetBrains/skills/tree/main/java-kotlin-migration-assistant
Command: npx skills add https://github.com/JetBrains/skills --skill java-kotlin-migration-assistant-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate Java code to Kotlin in Spring-based codebases without changing behavior, public contracts, framework compatibility, or binary assumptions unless explicitly intended. Use when converting classes incrementally, replacing Lombok patterns, managing platform types and nullability, preserving JPA and proxy behavior, or planning the safe migration order of a mixed Java and Kotlin codebase.

Core Features & Use Cases

Incremental migration of Java classes to Kotlin without altering runtime behavior
Replace Lombok patterns, manage platform types, and enforce nullability contracts
Plan and execute safe migrations across mixed Java/Kotlin modules with JPA/proxy considerations

Quick Start

Provide a Java project and ask to migrate a specific package from Java to Kotlin using the assistant to preserve behavior.

Frequently Asked Questions about java-kotlin-migration-assistant

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

FAQPage Schema

How do I safely migrate Java code to Kotlin in a Spring project without breaking behavior?▼

You can safely migrate Java to Kotlin in Spring by translating classes incrementally while enforcing nullability contracts, preserving JPA proxy behavior, and validating serialization to prevent runtime behavioral drift across the mixed codebase.

What is the best way to replace Lombok patterns when converting Java to Kotlin?▼

Replace Lombok patterns during Java to Kotlin migration by translating generated boilerplate into idiomatic Kotlin code while validating that public contracts, binary compatibility, and Spring framework annotations remain unchanged.

How does Kotlin handle Java platform types and nullability during a Spring codebase migration?▼

Kotlin handles Java platform types by enforcing explicit nullability contracts during migration, preventing null-pointer behavioral drift and preserving binary compatibility while translating Spring classes incrementally.

Can I gradually migrate a mixed Java and Kotlin module with JPA entities?▼

Yes, you can gradually migrate mixed Java and Kotlin modules by planning a safe migration order that preserves JPA and proxy behavior, ensuring entity contracts, annotations, and serialization logic remain compatible throughout the transition.

Why does my Kotlin migration break Spring proxy behavior and JPA compatibility?▼

Kotlin migration breaks Spring proxy behavior and JPA compatibility when classes convert without preserving binary assumptions or public contracts. The assistant prevents this by validating annotations, tests, and serialization behavior during translation.