Skillshub kotlin-tooling

Standards for Gradle Kotlin DSL, Version Catalogs, and MockK for Kotlin projects. Use when configuring build.gradle.kts, setting up libs.versions.toml, adding MockK for tests, or choosing between Kotlin-compatible test assertion libraries. (triggers: build.gradle.kts, libs.versions.toml, detekt.yml, mockk, kts, version catalog, kotest)

install
source · Clone the upstream repo
git clone https://github.com/ComeOnOliver/skillshub
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ComeOnOliver/skillshub "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/HoangNguyen0403/agent-skills-standard/kotlin-tooling" ~/.claude/skills/comeonoliver-skillshub-kotlin-tooling && rm -rf "$T"
manifest: skills/HoangNguyen0403/agent-skills-standard/kotlin-tooling/SKILL.md
source content

Kotlin Tooling Standards

Priority: P2 (RECOMMENDED)

Consistent build and quality verification tools.

Implementation Guidelines

  • Gradle DSL: Use Kotlin DSL (
    build.gradle.kts
    ) exclusively — 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, readable test output.

Anti-Patterns

  • No Groovy Gradle: Use Kotlin DSL (build.gradle.kts) exclusively; avoid legacy build.gradle.
  • No Mockito in Kotlin:
    when/then
    conflicts with Kotlin
    when
    ; use MockK (
    every/verify
    ).
  • No Hardcoded Versions: Manage all versions in libs.versions.toml; never inline in build files.

References