> kotlin-tooling

Build tools (Gradle KTS), Static Analysis (Detekt), and Testing standards. Use when configuring Gradle KTS build scripts, Detekt rules, or Kotlin build tooling. (triggers: build.gradle.kts, libs.versions.toml, detekt.yml, gradle, kts, detekt, mockk, junit)

fetch
$curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/kotlin-tooling?format=md"
SKILL.mdkotlin-tooling

Kotlin Tooling Standards

Priority: P2 (RECOMMENDED)

Consistent build and quality verification tools.

Implementation Guidelines

  • Gradle DSL: Use Kotlin DSL (build.gradle.kts) exclusively. It provides type safety and better IDE support.
  • Version Management: Use Version Catalogs (libs.versions.toml).
  • Linter: Use Ktlint for formatting and Detekt for complexity/code-smell analysis.
  • Testing: Use MockK for mocking (first-class Kotlin support). Use JUnit 5.
  • Assertions: Use Truth or Kotest Assertions for fluent reading.

Anti-Patterns

  • Groovy Gradle: Avoid legacy build.gradle files.
  • Mockito (Java): Avoid Mockito if possible; when/then syntax conflicts with Kotlin when. Use MockK (every/verify).
  • Hardcoded Versions: Don't put versions in build files. Use the catalog.

Code

For full MockK testing templates and libs.versions.toml setup: references/testing-tooling.md

// Modern Gradle KTS + Version Catalog
dependencies {
    implementation(libs.kotlin.stdlib)
    testImplementation(libs.mockk)
}

// Concise MockK Verify
verify(exactly = 1) { repo.getUser("1") }

Related Topics

best-practices | testing

┌ stats

installs/wk0
░░░░░░░░░░
github stars341
██████████
first seenMar 17, 2026
└────────────

┌ repo

HoangNguyen0403/agent-skills-standard
by HoangNguyen0403
└────────────

┌ tags

└────────────