kotlin-review

You can review staged or changed Kotlin and Java code against repository-specific guidelines, safety rules, and testing policy using a structured review process. It evaluates full affected file context and produces a structured assessment with Must fix, Should fix, and Nits categories.

Safety rules checked during a Kotlin code review include reflection approval requirements, no telemetry, no blocking calls in coroutines, and dependency bump policy. It also verifies the absence of prohibited patterns like unjustified non-null assertions.

Yes, the code review enforces testing policy by ensuring functional changes have Kotest-based assertions with stubs rather than mocks. It validates testing compliance as part of the PR readiness assessment.

To check if a version bump is required, the review process enforces a version gate when a root version.gradle.kts file exists in the repository. It validates whether user-visible version changes are needed based on the staged modifications.

Yes, you can review both Java and Kotlin code together for non-trivial edits and pre-PR checks. The review filters out config-distributed files and evaluates the full context of affected files to produce an approval verdict.

The best way to enforce coding guidelines and immutability is through a guideline-driven review checklist that verifies Kotlin idioms, formatting expectations, and prohibited patterns. It provides a structured assessment with quoted file and line evidence ending with an approval verdict.