spring-kotlin-code-review

Review Kotlin and Spring changes for transactional, proxy, and security issues.

14|1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/kbrgnj/kotlin-backend-agent-skills --skill spring-kotlin-code-review-kbrgnj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spring-kotlin-code-review
Source: https://github.com/kbrgnj/kotlin-backend-agent-skills/tree/main/.agents/skills/spring-kotlin-code-review
Command: npx skills add https://github.com/kbrgnj/kotlin-backend-agent-skills --skill spring-kotlin-code-review-kbrgnj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review Kotlin + Spring changes for behavioral regressions, transaction and proxy issues, API and serialization mistakes, persistence risks, security vulnerabilities, configuration drift, and missing tests. Use when reviewing a PR, diff, patch, or design change where generic style-focused review would miss Spring-specific correctness and operational risks.

Core Features & Use Cases

  • Systematic evaluation of behavioral changes across service layers for Spring-specific correctness (transactions, proxies, security, and configuration).
  • Immediate identification of regressions, misconfigurations, or missing tests, with prioritized findings.
  • Use Case: When reviewing a PR affecting transactional boundaries or security configuration.

Quick Start

Provide a thorough Spring-aware review of the given Kotlin change and summarize actionable findings.

Frequently Asked Questions about spring-kotlin-code-review

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

FAQPage Schema
How do I review Kotlin Spring changes for transactional and proxy issues?

Reviewing Kotlin Spring changes involves evaluating diffs for transaction boundaries, proxy invocation safety, and API contracts. This identifies behavioral regressions and Spring-specific correctness risks, outputting prioritized findings for remediation.

What common security vulnerabilities should I look for in a Spring Kotlin code review?

When checking security vulnerabilities in a Spring Kotlin code review, target security posture, configuration drift, and serialization mistakes. This reveals operational risks that generic style-focused reviews often miss.

Can I use a generic code review tool for Spring-specific persistence and configuration risks?

Generic code review tools typically miss Spring-specific persistence and configuration risks. Applying a specialized review to Kotlin PR diffs uncovers transactional misconfigurations and missing tests that generic reviews overlook.

How do I check for missing tests in a Kotlin Spring pull request?

Checking for missing tests in a Kotlin Spring pull request requires evaluating patches against service layer behavioral changes. This enforces test coverage checks and highlights gaps alongside transactional and security findings.

What is the best way to identify serialization mistakes in Spring Kotlin projects?

Identifying serialization mistakes in Spring Kotlin projects requires systematically evaluating API contracts and persistence changes. This process spots serialization errors and prioritizes them within the code review findings.

Why does my Spring Kotlin transaction proxy fail after a code change?

Spring Kotlin transaction proxies often fail after code changes due to proxy invocation safety issues or broken transaction boundaries. Reviewing the PR diff for these behavioral regressions isolates and resolves the failure.