Spring Kotlin Code Review
Review Kotlin + Spring changes for behavioral regressions, transaction and proxy bugs, API and serialization mistakes, persistence risks, security issues, 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.
Install
npx skills add JetBrains/skills --skill spring-kotlin-code-reviewgit clone --depth 1 https://github.com/JetBrains/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/spring-kotlin-code-review ~/.claude/skills/spring-kotlin-code-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Spring Kotlin Code Review Source mapping: Tier 1 critical skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-21`). ## Mission Review changes the way a strong Kotlin plus Spring teammate would review them: behavior first, risk first, evidence first. Optimize for catching bugs, regressions, and missing tests, not for polishing style. ## Read In This Order - Diff or changed files. - Related tests. - Configuration or build file changes. - Impacted controllers, services, repositories, security config, and migrations. - Project conventions from `project-context-ingestion` if available. ## Review Dimensions Check every relevant change for: - transaction boundaries and rollback behavior - proxy compatibility and self-invocation traps - bean wiring and configuration safety - API contract, validation, and serialization correctness - JPA or repository correctness and performance - security exposure and authorization drift - concurrency, retries, and idempotency risks - observability regressions - test adequacy and missing failure-path coverage - Kotlin-specific problems such as `!!`, unsafe platform types, and misuse of `lateinit` ## Output Contract Return findings first and order them by severity. Use this structure: - `Findings`: each finding should name the risk, explain the consequence, and point to the relevant file and line when available. - `Open questions or assumptions`: only where uncertainty changes the review outcome.
Details
- Skill name
spring-kotlin-code-review- Repository
- JetBrains/skills
- Path
spring-kotlin-code-review/SKILL.md- Repo updated
- 21 October 2026
FAQ
What does the Spring Kotlin Code Review skill do?
Review Kotlin + Spring changes for behavioral regressions, transaction and proxy bugs, API and serialization mistakes, persistence risks, security issues, 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.
How do I install the Spring Kotlin Code Review skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add JetBrains/skills --skill spring-kotlin-code-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Spring Kotlin Code Review popular?
It lives in JetBrains/skills, which has 398 GitHub stars and 35 forks.
Related skills
Deploy to Vercel
398JetBrains/skills
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
Vercel React Native Skills
398JetBrains/skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
Vitest
398JetBrains/skills
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
Using Git Worktrees
193MavCui/Agent-Skills-Hunter
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Skillshare Changelog
398JetBrains/skills
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: write release notes, generate a changelog, prepare a version release, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed since last release", or "prepare release notes", this is the skill to use. Do NOT manually edit CHANGELOG.md without this skill — it ensures proper formatting, user-perspective writing, and website changelog sync.
Yeet
398JetBrains/skills
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.