kotlin-project-code-review

Identify architectural drift and maintainability risks in Kotlin Multiplatform code reviews.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/leogallego/ansible-jane --skill kotlin-project-code-review-leogallego
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-project-code-review
Source: https://github.com/leogallego/ansible-jane/tree/main/skills/kotlin-kmp-code-review
Command: npx skills add https://github.com/leogallego/ansible-jane --skill kotlin-project-code-review-leogallego

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kotlin Multiplatform and Compose Multiplatform projects often suffer from architectural drift, fragmented responsibilities, and evolving code that becomes hard to maintain as shared and platform-specific layers diverge. This Skill provides a structured review framework to surface boundaries, ownership, and design invariants so teams can evolve code safely and consistently.

Core Features & Use Cases

  • Architectural drift detection across shared and platform-specific modules, boundaries, and responsibilities.
  • Guidance to preserve separation of concerns, place business logic in the right layer, and strengthen state management and testability.
  • Use Case: during PR reviews, bug fixes, or refactors, identify risky changes, propose targeted improvements, and enforce consistent architectural patterns.

Quick Start

Inspect a Kotlin Multiplatform PR to surface architecture drift and maintainability risks, then document actionable follow-ups.

Frequently Asked Questions about kotlin-project-code-review

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

FAQPage Schema
How do I detect architectural drift in Kotlin Multiplatform code during a PR review?

Architectural drift in Kotlin Multiplatform code is detected by reviewing PR changes across module boundaries and shared versus platform-specific layers, evaluating separation of concerns, state management, and concurrency to surface risky structural changes and maintainability issues.

What is architectural drift in Kotlin Multiplatform projects and when does it happen?

Architectural drift in Kotlin Multiplatform projects is the gradual fragmentation of responsibilities and divergence between shared and platform-specific layers. It occurs as code evolves without consistent boundaries, making the codebase hard to maintain and review safely.

How do I review Compose Multiplatform state management and separation of concerns?

Review Compose Multiplatform state management and separation of concerns by verifying business logic placement in the correct architectural layer, checking state ownership boundaries, and enforcing consistent design invariants across shared and platform-specific modules.

Can I use this code review framework for Kotlin Multiplatform bug fixes and refactoring?

Yes, this Kotlin Multiplatform code review framework is explicitly designed for use during bug fixes and refactoring. It helps identify risky boundary changes, propose targeted improvements, and enforce consistent architectural patterns across module and platform boundaries.

What's the best way to enforce consistent architecture across shared and platform-specific Kotlin modules?

The best way to enforce consistent architecture across shared and platform-specific Kotlin modules is to apply a structured review framework that evaluates ownership, design invariants, and separation of concerns during every PR, ensuring teams evolve code safely.

When should I trigger a deeper architectural review for Kotlin Multiplatform code?

A deeper architectural review for Kotlin Multiplatform code is warranted when standard PR reviews surface inconsistencies in separation of concerns, state management, concurrency, or testability across module boundaries and lifecycle-related concerns.