菜单
Use this skill when converting AssertJ assertions in Kotlin tests to Kotest matcher DSL. Apply it to Kotlin test files, preserve assertion semantics, and keep the test intent unchanged. Do not use this skill for JUnit assertEquals/assertNotNull migrations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill to convert a Java test into an equivalent Kotlin test. Reuse existing Kotlin test infrastructure by default, preserve behavior, and verify with focused test commands.
Use this skill when converting Java record DTOs or request/response models to Kotlin data classes that remain Java-friendly. Always add @JvmRecord, map nullability correctly, keep related domain models in the same Kotlin file, and add only safe defaults (prefer emptyList() or null, not generic String defaults).
Use this skill when converting Kotlin tests from JUnit assertions like assertEquals, assertNotNull, assertNull, assertTrue, assertFalse, and assertThrows to Kotest matcher DSL. Apply it to Kotlin test files and preserve behavior. Do not use this skill for AssertJ chain conversions.
Use this skill when implementing a type-safe Kotlin test data DSL for a selected subset of domain objects. Apply when tests need readable object graph construction and assembly (not just object creation). Ask for or infer the exact domain subset and build only that subset.
Use this skill when Kotlin test code contains duplicated setup or helper logic repeated at least 3 times. Create focused Kotlin extension functions (or small helper functions) to remove repetition while preserving test behavior and readability.
Use this skill when creating Kotlin Object Mother factory functions for test data objects (requests, DTOs, entities). Create Kotlin methods with default arguments for common values, nullable types for optional properties, and required non-null parameters without defaults for mandatory properties.
| name | kotest-from-assertj |
| description | Use this skill when converting AssertJ assertions in Kotlin tests to Kotest matcher DSL. Apply it to Kotlin test files, preserve assertion semantics, and keep the test intent unchanged. Do not use this skill for JUnit assertEquals/assertNotNull migrations. |
Convert AssertJ assertions in Kotlin tests into Kotest matcher DSL while preserving behavior and readability.
assertThat, assertThatThrownBy, chained assertions, extracting).references/rewrite-map.md.instance.apply { ... }.apply { ... } block in assertSoftly { ... }.assertEquals, assertNotNull, assertThrows).containsExactly(...) is order-sensitive.containsExactlyInAnyOrder(...) is order-insensitive.extracting(...) chains often become clearer as explicit property checks in Kotlin.items.map { it.name }.shouldContainAllInAnyOrder(...)assertThatThrownBy { ... } maps to shouldThrow<ExceptionType> { ... }.isNull vs isNotNull).result.apply { field1 shouldBe ...; field2.shouldNotBeNull() }Before:
assertThat(result.id).isNotNull()
assertThat(result.name).isEqualTo("Ada")
assertThat(tags).extracting { it.name }.containsExactlyInAnyOrder("kotlin", "testing")
assertThatThrownBy { service.create(invalidInput) }
.isInstanceOf(IllegalArgumentException::class.java)
.hasMessageContaining("invalid")
After:
result.id.shouldNotBeNull()
result.name shouldBe "Ada"
tags.map { it.name }.shouldContainAllInAnyOrder("kotlin", "testing")
shouldThrow<IllegalArgumentException> {
service.create(invalidInput)
}.message.shouldContain("invalid")
After rewrites:
Suggested command pattern:
./gradlew test --tests "*YourTestClassPattern*"
When reporting completion, include: