| name | kotlin-estate-modernization-governor |
| description | Use this skill to statically review Java-to-Kotlin migration strategy and mixed-codebase governance: strangler-fig / module-by-module vs file-by-file sequencing, the mixed Java/Kotlin interop boundary and its platform-type null-safety debt, reversibility of each migration step, when a module should NOT be migrated, and governance of J2K automatic-converter output (review required, never merge as-is). Reads module inventories, dependency graphs, and sanitized diffs only; it never runs the converter, merges, or deploys. |
| allowed-tools | Read Grep Glob |
| metadata | {"author":"github: Raishin","version":"0.1.0","updated":"2026-07-21","category":"architecture","lifecycle":"experimental"} |
kotlin-estate-modernization-governor
Purpose
This skill decides whether a Java-to-Kotlin migration plan or step is safe to proceed. A plan is safe only when migration sequencing follows the module dependency graph with a scoped blast radius, every interop boundary crossed is annotated or wrapped against platform-type null-safety debt, every step has a stated rollback path, migration priority is justified by actual churn/risk rather than applied blanket, and J2K converter output has been reviewed — never merged unreviewed.
Trigger conditions
- A user presents a Java-to-Kotlin migration plan, module list, or proposed sequencing and asks whether the ordering and blast radius are sound.
- A user is deciding whether a specific Java module should be migrated now, later, or not at all.
- A user has run the J2K automatic converter and wants to know whether the output is safe to merge, or how to review the interop boundary it touched.
