kta-code-review

Audit Kotlin code for idioms, correctness, architecture, concurrency, and safety.

4|Updated May 7, 2026
One-click install
npx skills add https://github.com/dantech0xff/dreams --skill kta-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kta-code-review
Source: https://github.com/dantech0xff/dreams/tree/main/.agents/skills/kta-code-review
Command: npx skills add https://github.com/dantech0xff/dreams --skill kta-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Senior Kotlin Code Reviewer provides a strict, language-agnostic evaluation of Kotlin code, identifying idioms, correctness gaps, architectural flaws, concurrency pitfalls, null-safety issues, testing gaps, performance hotspots, and potential security concerns, with citations to file:line anchors and minimal fixes.

Core Features & Use Cases

  • Framework-agnostic Kotlin review focusing on idioms, architecture, concurrency, null safety, testing, and performance.
  • Produces prioritized findings with file:line anchors and compact, minimal-diff fixes.
  • Use cases include reviewing a Kotlin file, a class, a module, a diff, a branch, or a pull request to produce actionable feedback.

Quick Start

Provide the Kotlin source or diff you want reviewed and I will return a file-and-line annotated critique with concrete, minimal fixes.

Frequently Asked Questions about kta-code-review

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

FAQPage Schema
How do I review Kotlin code for idioms and concurrency issues?

You can review Kotlin code for idioms and concurrency by providing your source files or pull requests to receive an annotated critique. The audit produces prioritized findings with file:line anchors, identifying concurrency pitfalls, architectural flaws, and null-safety issues alongside minimal-diff fixes.

What is the best way to audit a Kotlin pull request for null safety and architecture?

The best way to audit a Kotlin pull request for null safety and architecture is to apply a strict, framework-agnostic code review. This evaluates the diff for idiomatic correctness and architectural flaws, delivering prioritized issues with concrete, minimal fixes and defensible rationale.

Can I use this Kotlin code review on a specific branch diff without a DI framework?

Yes, you can review a specific branch diff without a DI framework because the evaluation is strictly framework-agnostic. It respects Kotlin language best practices and does not rely on any specific DI or UI stack to produce file:line annotated findings and minimal fixes.

How do I get actionable fixes for Kotlin static analysis findings?

To get actionable fixes for Kotlin static analysis findings, submit your source file, class, or module for review. The process delivers file:line annotated findings with prioritized issues and compact, minimal-diff fixes that address performance hotspots, testing gaps, and security concerns.

What are the limitations of framework-agnostic Kotlin code reviews?

The limitation of framework-agnostic Kotlin code reviews is that they do not rely on or evaluate any specific DI or UI stack. The review strictly focuses on language-level best practices, idioms, and concurrency, meaning stack-specific integration issues will not be covered in the annotated findings.