kotlin-reviewer

Review Kotlin and Spring Boot pull requests for architecture, tests, and security.

7|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/pranav8494/team-of-agents --skill kotlin-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-reviewer
Source: https://github.com/pranav8494/team-of-agents/tree/main/skills/kotlin-code-reviewer
Command: npx skills add https://github.com/pranav8494/team-of-agents --skill kotlin-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you perform consistent, production-grade reviews of Kotlin/Spring Boot pull requests so architectural violations, missing tests, and security flaws don’t slip into main.

Core Features & Use Cases

  • Architecture boundary enforcement: Ensures controllers/services/adapters follow clear responsibility rules and blocks boundary-breaking changes.
  • Kotlin correctness & idiom checks: Flags problematic patterns (null handling, mutability, logging, coroutine misuse) and recommends idiomatic replacements.
  • Testing, observability, and security gatekeeping: Verifies required test coverage, confirms metrics/logging conventions, and escalates security issues as blockers.
  • Use case: Review a PR that changes payment-related logic and touches controller/service/client/repository code, and get a structured phased review plus an explicit merge verdict.

Quick Start

Ask an AI to review your Kotlin/Spring Boot PR diff using the kotlin-reviewer skill and to produce a five-phase report ending with an approve or request-changes verdict.

Frequently Asked Questions about kotlin-reviewer

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

FAQPage Schema
How do I review Kotlin Spring Boot pull requests for architectural boundary breaks?

Review Kotlin Spring Boot pull requests by applying a phased checklist that verifies controller, service, and adapter responsibility rules to block architectural boundary breaks before merging code into main.

What is the best way to check Kotlin PRs for missing test coverage and security flaws?

Checking Kotlin PRs for missing test coverage and security flaws requires a structured review workflow that verifies required tests, confirms logging conventions, and escalates security regressions as blocking merge verdicts.

Can I enforce Kotlin idiom checks and null handling during a code review?

You can enforce Kotlin idiom checks during code review by flagging problematic patterns like improper null handling, mutability, logging, and coroutine misuse, then applying idiomatic replacements.

Does a Spring Boot code review verify observability and metrics conventions?

A Spring Boot code review verifies observability by checking that pull requests confirm required metrics and logging conventions, ensuring production-grade monitoring is maintained across architectural boundaries.

How do I get an explicit merge verdict after reviewing a Kotlin PR diff?

Get an explicit merge verdict after reviewing a Kotlin PR diff by running a five-phase review checklist that produces severity labels and concludes with a final approve or request-changes decision.