[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M786K41633Q2CJN2GGAMTG02":3,"skill-same:01M786K41633Q2CJN2GGAMTG02":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M786K41633Q2CJN2GGAMTG02","kotlin-testing",null,"Use ONLY when user explicitly requests Kotlin test code, Kotest\u002FMockK configuration, test failure diagnosis, or coverage improvement for Kotlin projects.\nTriggers: \"write test kotlin\", \"kotest\", \"mockk\", \"coroutine test\", \"kotlin coverage\", \"runTest\", \"property testing kotlin\", \"ActivityScenario\".\nDo NOT activate for: general Kotlin coding without test context, Gradle build errors, Kotlin multiplatform setup, or Android UI implementation without test needs.","chenziyang110\u002Flaunchdeck","chenziyang110","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43693913?v=4","01M7863EBWK1D0P6A29YGEMAS4","Robin11","01M7863ECM1VB6RXDMHTW90D2T",0,"MIT","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fkotlin-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"kotlin-testing\"\ndescription: \"Use ONLY when user explicitly requests Kotlin test code, Kotest\u002FMockK configuration,\ntest failure diagnosis, or coverage improvement for Kotlin projects.\n\nTriggers: \\\"write test kotlin\\\", \\\"kotest\\\", \\\"mockk\\\", \\\"coroutine test\\\",\n\\\"kotlin coverage\\\", \\\"runTest\\\", \\\"property testing kotlin\\\", \\\"ActivityScenario\\\".\n\nDo NOT activate for: general Kotlin coding without test context, Gradle build\nerrors, Kotlin multiplatform setup, or Android UI implementation without test needs.\n\"\ncompatibility: \"Requires spec-kit project structure with .specify\u002F directory\"\nmetadata:\n  author: \"github-spec-kit\"\n  source: \"templates\u002Fpassive-skills\u002Fkotlin-testing\u002FSKILL.md\"\n---\n\n\n# Kotlin Testing (Agent Skill)\n\nAgent-focused testing workflow for modern Kotlin using Kotest, the most feature-rich Kotlin-native test framework, with MockK for mocking.\n\n## When to Use\n\n- Writing new Kotlin tests or fixing existing tests\n- Designing unit\u002Fintegration test coverage for Kotlin components\n- Adding test coverage, CI gating, or regression protection\n- Configuring Kotest\u002FMockK workflows for consistent execution\n- Investigating test failures or flaky behavior\n- Testing Android, Ktor, Spring Boot, or Kotlin Multiplatform\n\n### When NOT to Use\n\n- Implementing new product features without test changes\n- Large-scale refactors unrelated to test coverage or failures\n- Performance tuning without test regressions to validate\n- Non-Kotlin projects or non-test tasks\n\n### Stop Conditions — When to ASK instead of generating\n\nBefore generating any test code, STOP and ask the user if:\n- The code under test has **zero testability** (object singletons everywhere, no DI, hard-coded network calls in ViewModels)\n- **No test framework** is detected (no Kotest\u002FMockK in build.gradle.kts, no test source set)\n- The request is **ambiguous**: \"test my app\" or \"add tests\" without specifying files or classes\n- A **required test dependency** (Kotest, MockK, kotlinx-coroutines-test) is not installed\n- The test would require **secrets, real credentials, or production database access**\n\n## Core Concepts\n\n- **TDD loop**: red → green → refactor (tests first, minimal fix, then cleanups).\n- **Kotest styles**: `FunSpec`, `StringSpec`, `DescribeSpec`, `BehaviorSpec`, etc.\n- **Property testing**: built-in property-based testing via `forAll`.\n- **Test layout**: `src\u002Ftest\u002Fkotlin\u002F` mirroring source package structure.\n- **Mocks**: `MockK` with Kotlin-friendly DSL for mocks, spies, and co-routines.\n- **CI signal**: `.\u002Fgradlew test` with `--info` output.\n\n## Agent Execution Protocol\n\nWhen this skill is activated, follow this exact execution sequence:\n\n### Phase 1: Context Analysis\nBefore writing any test code:\n1. Identify the Kotlin version (2.0+) and build tool (Gradle).\n2. Check for existing test files (`src\u002Ftest\u002Fkotlin\u002F`) to infer style (Kotest, JUnit 5, MockK).\n3. Analyze the code under test: identify public API surface, coroutines (`suspend` functions), side effects, and Android\u002FKtor\u002FSpring context.\n4. Determine request type: (a) new tests, (b) fixing broken tests, (c) coverage improvement, (d) flaky test diagnosis.\n\n### Phase 2: Strategy Selection\nBased on Phase 1, select the appropriate strategy:\n- **Pure functions \u002F value objects**: unit tests only, no mocks needed. Use Kotest `FunSpec` or JUnit 5 `@Test`.\n- **External dependencies (DB, HTTP, filesystem)**: use **MockK** for Kotlin-friendly mocking; prefer `kotlinx-coroutines-test` for coroutine testing.\n- **Android components**: use `ActivityScenario` for UI tests; use `UnconfinedTestDispatcher` \u002F `StandardTestDispatcher` for coroutine tests.\n- **Async \u002F coroutine code**: use `runTest { }` from `kotlinx-coroutines-test`; never use `runBlocking` in tests.\n\n### Decision Tree (Complex Scenarios)\n\n```text\nQ1: External I\u002FO (DB, HTTP, filesystem, network)?\n  → Yes → Q2\n  → No  → Pure unit test, no mocks needed\n\nQ2: Mockable (interface, DI, Koin\u002FKodein)?\n  → Yes → Mock at boundary (MockK mockk\u003CT>, coEvery\u002FcoVerify)\n  → No  → Q3\n\nQ3: Coroutine\u002Fsuspend function?\n  → Yes → runTest { } with StandardTestDispatcher\n  → No  → Q4\n\nQ4: Android component (Activity, ViewModel)?\n  → Yes → ActivityScenario + StandardTestDispatcher\n  → No  → Q5\n\nQ5: Property-based needed?\n  → Yes → Kotest forAll \u002F checkAll\n  → No  → Standard FunSpec\u002FDescribeSpec\n```\n\n### Phase 3: Test Case Design\nApply systematic test design before coding:\n1. **Happy path**: normal input → expected output.\n2. **Boundary values**: empty lists, `null`, empty strings, `Int.MAX_VALUE`, `LocalDate.MIN`.\n3. **Error cases**: exceptions (`shouldThrow`), validation errors, cancellation exceptions, timeout scenarios.\n4. **Concurrency**: coroutine leaks, flow emission ordering, shared mutable state in `MutableStateFlow`.\n\n### Phase 4: Code Generation\nOutput tests in this exact structure:\n```\n#### Test Strategy Summary\n- [ ] Scope: Unit \u002F Integration \u002F Android UI\n- [ ] Framework: Kotest + MockK (or JUnit 5 + MockK for mixed projects)\n- [ ] Mocking: Yes\u002FNo — MockK \u002F fakes\n- [ ] Edge cases covered: \u003Clist>\n\n#### Generated Test Code\n\u003Cfile_path>\n\u003Ccode>\n\n#### Running Commands\n```bash\n.\u002Fgradlew test --tests \"*ClassName*\"\n.\u002Fgradlew test --info\n```\n\n#### Coverage Impact (if applicable)\n- Estimated coverage change: \u003CX%>\n- Command to verify: `.\u002Fgradlew test jacocoTestReport`\n```\n\n### Phase 5: Verification Checklist\nBefore completing, verify:\n- [ ] Tests compile and pass (`.\u002Fgradlew test`).\n- [ ] Each test has exactly one logical assertion focus.\n- [ ] Mocks are cleared between tests (`clearAllMocks()` in `afterTest`).\n- [ ] No `Thread.sleep` used in coroutine tests (use `runTest` with `advanceTimeBy`).\n- [ ] Flaky test guardrails applied (deterministic data, no real network in unit tests).\n\n## TDD Workflow\n\n```kotlin\n\u002F\u002F src\u002Ftest\u002Fkotlin\u002Fcom\u002Fexample\u002FAddTest.kt\nfun add(a: Int, b: Int): Int = TODO() \u002F\u002F stub\n\nclass AddTest : FunSpec({\n    test(\"adds two numbers\") { \u002F\u002F RED\n        add(2, 3) shouldBe 5\n    }\n})\n\n\u002F\u002F src\u002Fmain\u002Fkotlin\u002Fcom\u002Fexample\u002FMath.kt\nfun add(a: Int, b: Int): Int = a + b \u002F\u002F GREEN\n\n\u002F\u002F REFACTOR: simplify\u002Frename once tests pass\n```\n\n## Code Examples\n\n### Basic Unit Test (Kotest FunSpec)\n\n```kotlin\nimport io.kotest.core.spec.style.FunSpec\nimport io.kotest.matchers.shouldBe\n\nclass CalculatorTest : FunSpec({\n    test(\"adds two numbers\") {\n        Calculator.add(2, 3) shouldBe 5\n    }\n\n    test(\"handles negative numbers\") {\n        Calculator.add(-1, 1) shouldBe 0\n    }\n})\n```\n\n### DescribeSpec (BDD Style)\n\n```kotlin\nimport io.kotest.core.spec.style.DescribeSpec\nimport io.kotest.matchers.shouldBe\nimport io.kotest.matchers.shouldNotBe\n\nclass UserStoreTest : DescribeSpec({\n    lateinit var store: UserStore\n\n    beforeTest {\n        store = UserStore()\n        store.seed(listOf(User(\"alice\"), User(\"bob\")))\n    }\n\n    describe(\"find user\") {\n        it(\"should return existing user\") {\n            val user = store.find(\"alice\")\n            user shouldNotBe null\n            user?.name shouldBe \"alice\"\n        }\n\n        it(\"should return null for missing user\") {\n            store.find(\"charlie\") shouldBe null\n        }\n    }\n})\n```\n\n### Mocking (MockK)\n\n```kotlin\nimport io.mockk.*\nimport io.kotest.core.spec.style.FunSpec\nimport io.kotest.matchers.shouldBe\n\ninterface Notifier {\n    fun send(message: String)\n}\n\nclass Service(private val notifier: Notifier) {\n    fun publish(message: String) = notifier.send(message)\n}\n\nclass ServiceTest : FunSpec({\n    test(\"sends notifications\") {\n        val notifier = mockk\u003CNotifier>()\n        every { notifier.send(\"hello\") } just Runs\n        val service = Service(notifier)\n\n        service.publish(\"hello\")\n\n        verify(exactly = 1) { notifier.send(\"hello\") }\n    }\n})\n```\n\n### Coroutine Test\n\n```kotlin\nimport io.kotest.core.spec.style.FunSpec\nimport io.kotest.matchers.shouldBe\nimport io.kotest.assertions.timing.eventually\nimport kotlin.time.Duration.Companion.seconds\n\nclass ApiTest : FunSpec({\n    test(\"fetches user data\") {\n        eventually(5.seconds) {\n            val user = fetchUser(\"1\")\n            user.name shouldBe \"alice\"\n        }\n    }\n})\n```\n\n### Property-Based Testing (Kotest)\n\n```kotlin\nimport io.kotest.core.spec.style.FunSpec\nimport io.kotest.property.Arb\nimport io.kotest.property.arbitrary.int\nimport io.kotest.property.forAll\nimport io.kotest.matchers.shouldBe\n\nclass MathPropertyTest : FunSpec({\n    test(\"add is commutative\") {\n        forAll(Arb.int(), Arb.int()) { a, b ->\n            Math.add(a, b) == Math.add(b, a)\n        }\n    }\n})\n```\n\n### StringSpec (Simple Tests)\n\n```kotlin\nimport io.kotest.core.spec.style.StringSpec\nimport io.kotest.matchers.string.shouldContain\n\nclass ValidationTest : StringSpec({\n    \"should reject negative age\" {\n        shouldThrow\u003CIllegalArgumentException> {\n            Validator.validateAge(-1)\n        }.message shouldContain \"non-negative\"\n    }\n})\n```\n\n### Data-Driven Test\n\n```kotlin\nimport io.kotest.core.spec.style.FunSpec\nimport io.kotest.matchers.shouldBe\nimport io.kotest.datatest.withData\n\nclass MathParamTest : FunSpec({\n    context(\"add function\") {\n        withData(\n            nameFn = { \"${it.a} + ${it.b} = ${it.expected}\" },\n            TestCase(1, 2, 3),\n            TestCase(-1, 1, 0),\n            TestCase(0, 0, 0),\n            TestCase(100, 200, 300),\n        ) { (a, b, expected) ->\n            Math.add(a, b) shouldBe expected\n        }\n    }\n}) {\n    data class TestCase(val a: Int, val b: Int, val expected: Int)\n}\n```\n\n## Build Configuration (Gradle)\n\n```kotlin\n\u002F\u002F build.gradle.kts\nplugins {\n    kotlin(\"jvm\") version \"2.0.0\"\n}\n\ndependencies {\n    testImplementation(\"io.kotest:kotest-runner-junit5:5.9.0\")\n    testImplementation(\"io.kotest:kotest-assertions-core:5.9.0\")\n    testImplementation(\"io.kotest:kotest-property:5.9.0\")\n    testImplementation(\"io.kotest:kotest-framework-datatest:5.9.0\")\n    testImplementation(\"io.mockk:mockk:1.13.12\")\n    testImplementation(\"org.jetbrains.kotlinx:kotlinx-coroutines-test:1.10.0\")\n}\n\ntasks.test {\n    useJUnitPlatform()\n    testLogging {\n        events(\"passed\", \"skipped\", \"failed\")\n    }\n}\n```\n\n## Running Tests\n\n```bash\n.\u002Fgradlew test                         # all tests\n.\u002Fgradlew test --tests \"*CalculatorTest*\"\n.\u002Fgradlew test --info                  # verbose output\n.\u002Fgradlew test --continuous            # watch mode\n.\u002Fgradlew test -Dkotest.tags=\"Integration\"\n```\n\n## Coverage\n\n```kotlin\n\u002F\u002F build.gradle.kts — JaCoCo\nplugins {\n    id(\"jacoco\")\n}\n\ntasks.jacocoTestReport {\n    dependsOn(tasks.test)\n    reports {\n        xml.required.set(true)\n        html.required.set(true)\n    }\n}\n```\n\n```bash\n.\u002Fgradlew test jacocoTestReport\n```\n\n## CI\u002FCD Integration (GitHub Actions)\n\n```yaml\n# .github\u002Fworkflows\u002Ftest.yml\nname: Test\non: [push, pull_request]\njobs:\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-java@v4\n        with: { java-version: '21', distribution: 'temurin' }\n      - run: .\u002Fgradlew test jacocoTestReport\n      - uses: actions\u002Fupload-artifact@v4\n        if: always()\n        with: { name: test-results, path: '**\u002Ftest-results\u002F**\u002F*.xml' }\n```\n\n## Flaky Tests Guardrails\n\n- Never use `Thread.sleep()` in coroutine tests; use `kotlinx.coroutines.test`.\n- Use `UnconfinedTestDispatcher` or `StandardTestDispatcher` for controlled coroutine scope.\n- Make temp files unique with `createTempFile()` \u002F `createTempDir()`.\n- Mock `kotlinx.datetime.Clock` for time-dependent code.\n\n## Test Case Design Patterns\n\nApply these systematic patterns before writing test code to ensure robust coverage beyond the happy path.\n\n### 1. Boundary Value Analysis\nTest at the edges of valid input domains: empty, zero, maximum, null, and just-outside valid ranges.\n\n```kotlin\n\u002F\u002F src\u002Ftest\u002Fkotlin\u002Fcom\u002Fexample\u002FValidatorTest.kt\nclass ValidatorTest : FunSpec({\n    context(\"input validation\") {\n        withData(\n            nameFn = { \"rejects ${it.name}\" },\n            TestCase(\"\", \"empty\"),\n            TestCase(\" \", \"whitespace\"),\n            TestCase(\"a\".repeat(10001), \"too long\")\n        ) { (input, _) ->\n            shouldThrow\u003CIllegalArgumentException> { validator.validate(input) }\n        }\n    }\n}) {\n    data class TestCase(val input: String, val name: String)\n}\n```\n\n### 2. Negative \u002F Error Case Testing\nVerify the system behaves correctly under invalid or unexpected conditions.\n\n```kotlin\nclass CalculatorTest : FunSpec({\n    test(\"throws on divide by zero\") {\n        shouldThrow\u003CArithmeticException> { calculator.divide(10, 0) }\n    }\n})\n```\n\n### 3. State-Based Testing\nFor objects with internal state, verify transitions between states are correct and irreversible where expected.\n\n```kotlin\nclass ConnectionTest : FunSpec({\n    test(\"state transitions are correct\") {\n        val conn = Connection()\n        conn.state shouldBe State.CLOSED\n        conn.open()\n        conn.state shouldBe State.OPEN\n        conn.close()\n        conn.state shouldBe State.CLOSED\n        \u002F\u002F Idempotency\n        conn.close()\n        conn.state shouldBe State.CLOSED\n    }\n})\n```\n\n## Common Test Smells to Avoid\n\n- **Assertion Roulette**: Many assertions without descriptive messages, making failure diagnosis ambiguous. *Fix: Use Kotest `\"value\" shouldBe expected` with descriptive test names.*\n- **Happy Path Bias**: Only testing successful scenarios, leaving error paths uncovered. *Fix: Test `null` values, exceptions with `shouldThrow\u003C>`, edge inputs.*\n- **Mock Overdose**: Too many mocks hiding integration issues or coupling tests to implementation. *Fix: Mock only at architectural boundaries (repositories, services); use `relaxed = true` only when needed.*\n- **The Free Ride**: Tests that execute code but assert nothing meaningful. *Fix: Every test must have at least one specific, falsifiable assertion.*\n- **Obscure Test**: Long test functions with no clear arrange\u002Fact\u002Fassert structure. *Fix: Follow AAA, choose a consistent spec style (FunSpec\u002FDescribeSpec), keep tests focused.*\n- **Flaky Test**: Non-deterministic results from coroutines, time, or shared state. *Fix: Use `runTest { }` with `UnconfinedTestDispatcher`, `clearAllMocks()` between tests.*\n\n## Best Practices\n\n### DO\n\n- Use Kotest style specs that match your team's preference (FunSpec for simple, DescribeSpec for BDD)\n- Use `shouldBe`, `shouldNotBe`, `shouldThrow` from Kotest matchers\n- Use coroutine test dispatchers instead of `runBlocking`\n- Use property-based testing for invariant validation\n- Use `withData` for readable parametrized tests\n\n### DON'T\n\n- Don't use `Thread.sleep()` for synchronization in coroutine tests\n- Don't mix JUnit 4 and Kotest annotations\n- Don't mock value objects or data classes\n- Don't use `runBlocking` in tests — use coroutine test dispatchers\n- Don't over-use `io.mockk.every` for simple return values\n\n### Common Pitfalls\n\n- **Coroutine leaks** → Always use `runTest` from `kotlinx-coroutines-test`.\n- **Flaky time-based tests** → Use `TestDispatcher` with `advanceTimeBy()`.\n- **MockK leaks** → Use `clearAllMocks()` in `afterProject` or `afterTest`.\n- **Android instrumentation** → Use `@MediumTest` \u002F `@LargeTest` annotations.\n\n### Android Testing (ActivityScenario + Espresso)\n\n```kotlin\n\u002F\u002F app\u002Fsrc\u002FandroidTest\u002Fkotlin\u002FLoginActivityTest.kt\nimport androidx.test.ext.junit.runners.AndroidJUnit4\nimport androidx.test.core.app.ActivityScenario\nimport androidx.test.espresso.Espresso.onView\nimport androidx.test.espresso.action.ViewActions.*\nimport androidx.test.espresso.assertion.ViewAssertions.matches\nimport androidx.test.espresso.matcher.ViewMatchers.*\nimport org.junit.Test\nimport org.junit.runner.RunWith\n\n@RunWith(AndroidJUnit4::class)\nclass LoginActivityTest {\n\n    @Test\n    fun testSuccessfulLogin() {\n        val scenario = ActivityScenario.launch(LoginActivity::class.java)\n\n        onView(withId(R.id.emailInput))\n            .perform(typeText(\"user@example.com\"))\n        onView(withId(R.id.passwordInput))\n            .perform(typeText(\"password123\"))\n        onView(withId(R.id.loginButton))\n            .perform(click())\n        onView(withId(R.id.welcomeText))\n            .check(matches(withText(\"Welcome!\")))\n\n        scenario.close()\n    }\n}\n```\n\n> **build.gradle.kts dependencies**: Add `androidx.test:core-ktx:1.6.x`, `androidx.test.espresso:espresso-core:3.6.x`, `androidx.test:runner:1.6.x` for androidTest source set.\n\n## Mutation Testing (PIT)\n\n```kotlin\n\u002F\u002F build.gradle.kts\nplugins {\n    id(\"info.solidsoft.pitest\") version \"1.15.0\"\n}\n\npitest {\n    targetClasses.set(listOf(\"com.example.*\"))\n    mutators.set(listOf(\"STRONGER\"))\n    outputFormats.set(listOf(\"HTML\"))\n}\n```\n\n```bash\n.\u002Fgradlew pitest\n# Report: build\u002Freports\u002Fpitest\u002Findex.html\n```\n\n> Mutation testing verifies tests catch bugs by introducing code mutations (e.g., `+` → `-`). **Target ≥80% mutation score** for business logic.\n\n## Alternatives\n\n- **JUnit 5 + MockK**: Simpler setup, JUnit-compatible, good for mixed Java\u002FKotlin projects.\n- **Spek**: Structure-based testing with `@Describe` \u002F `@It` annotations.\n- **Turbine**: Kotlin Flow testing.\n","# Kotlin Testing (Agent Skill)\n\nAgent-focused testing workflow for modern Kotlin using Kotest, the most feature-rich Kotlin-native test framework, with MockK for mocking.\n\n## When to Use\n\n- Writing new Kotlin tests or fixing existing tests\n- Designing unit\u002Fintegration test coverage for Kotlin components\n- Adding test coverage, CI gating, or regression protection\n- Configuring Kotest\u002FMockK workflows for consistent execution\n- Investigating test failures or flaky behavior\n- Testing Android, Ktor, Spring Boot, or Kotlin Multiplatform\n\n### When NOT to Use\n\n- Implementing new product features without test changes\n- Large-scale refactors unrelated to test coverage or failures\n- Performance tuning without test regressions to validate\n- Non-Kotlin projects or non-test tasks\n\n### Stop Conditions — When to ASK instead of generating\n\nBefore generating any test code, STOP and ask the user if:\n- The code under test has **zero testability** (object singletons everywhere, no DI, hard-coded network calls in ViewModels)\n- **No test framework** is detected (no Kotest\u002FMockK in build.gradle.kts, no test source set)\n- The request is **ambiguous**: \"test my app\" or \"add tests\" without specifying files or classes\n- A **required test dependency** (Kotest, MockK, kotlinx-coroutines-test) is not installed\n- The test would require **secrets, real credentials, or production database access**\n\n## Core Concepts\n\n- **TDD loop**: red → green → refactor (tests first, minimal fix, then cleanups).\n- **Kotest styles**: `FunSpec`, `StringSpec`, `DescribeSpec`, `BehaviorSpec`, etc.\n- **Property testing**: built-in property-based testing via `forAll`.\n- **Test layout**: `src\u002Ftest\u002Fkotlin\u002F` mirroring source package structure.\n- **Mocks**: `MockK` with Kotlin-friendly DSL for mocks, spies, and co-routines.\n- **CI signal**: `.\u002Fgradlew test` with `--info` output.\n\n## Agent Execution Protocol\n\nWhen this skill is activated, follow this exact execution sequence:\n\n### Phase 1: Context Analysis\nBefore writing any test code:\n1. Identify the Kotlin version (2.0+) and build tool (Gradle).\n2. Check for existing test files (`src\u002Ftest\u002Fkotlin\u002F`) to infer style (Kotest, JUnit 5, MockK).\n3. Analyze the code under test: identify public API surface, coroutines (`suspend` functions), side effects, and Android\u002FKtor\u002FSpring context.\n4. Determine request type: (a) new tests, (b) fixing broken tests, (c) coverage improvement, (d) flaky test diagnosis.\n\n### Phase 2: Strategy Selection\nBased on Phase 1, select the appropriate strategy:\n- **Pure functions \u002F value objects**: unit tests only, no mocks needed. Use Kotest `FunSpec` or JUnit 5 `@Test`.\n- **External dependencies (DB, HTTP, filesystem)**: use **MockK** for Kotlin-friendly mocking; prefer `kotlinx-coroutines-test` for coroutine testing.\n- **Android components**: use `ActivityScenario` for UI tests; use `UnconfinedTestDispatcher` \u002F `StandardTestDispatcher` for coroutine tests.\n- **Async \u002F coroutine code**: use `runTest { }` from `kotlinx-coroutines-test`; never use `runBlocking` in tests.\n\n### Decision Tree (Complex Scenarios)\n\n```text\nQ1: External I\u002FO (DB, HTTP, filesystem, network)?\n  → Yes → Q2\n  → No  → Pure unit test, no mocks needed\n\nQ2: Mockable (interface, DI, Koin\u002FKodein)?\n  → Yes → Mock at boundary (MockK mockk\u003CT>, coEvery\u002FcoVerify)\n  → No  → Q3\n\nQ3: Coroutine\u002Fsuspend function?\n  → Yes → runTest { } with StandardTestDispatcher\n  → No  → Q4\n\nQ4: Android component (Activity, ViewModel)?\n  → Yes → ActivityScenario + StandardTestDispatcher\n  → No  → Q5\n\nQ5: Property-based needed?\n  → Yes → Kotest forAll \u002F checkAll\n  → No  → Standard FunSpec\u002FDescribeSpec\n```\n\n### Phase 3: Test Case Design\nApply systematic test design before coding:\n1. **Happy path**: normal input → expected output.\n2. **Boundary values**: empty lists, `null`, empty strings, `Int.MAX_VALUE`, `LocalDate.MIN`.\n3. **Error cases**: exceptions (`shouldThrow`), validation errors, cancellation exceptions, timeout scenarios.\n4. **Concurrency**: coroutine leaks, flow emission ordering, shared mutable state in `MutableStateFlow`.\n\n### Phase 4: Code Generation\nOutput tests in this exact structure:\n```\n#### Test Strategy Summary\n- [ ] Scope: Unit \u002F Integration \u002F Android UI\n- [ ] Framework: Kotest + MockK (or JUnit 5 + MockK for mixed projects)\n- [ ] Mocking: Yes\u002FNo — MockK \u002F fakes\n- [ ] Edge cases covered: \u003Clist>\n\n#### Generated Test Code\n\u003Cfile_path>\n\u003Ccode>\n\n#### Running Commands\n```bash\n.\u002Fgradlew test --tests \"*ClassName*\"\n.\u002Fgradlew test --info\n```\n\n#### Coverage Impact (if applicable)\n- Estimated coverage change: \u003CX%>\n- Command to verify: `.\u002Fgradlew test jacocoTestReport`\n```\n\n### Phase 5: Verification Checklist\nBefore completing, verify:\n- [ ] Tests compile and pass (`.\u002Fgradlew test`).\n- [ ] Each test has exactly one logical assertion focus.\n- [ ] Mocks are cleared between tests (`clearAllMocks()` in `afterTest`).\n- [ ] No `Thread.sleep` used in coroutine tests (use `runTest` with `advanceTimeBy`).\n- [ ] Flaky test guardrails applied (deterministic data, no real network in unit tests).\n\n## TDD Workflow\n\n```kotlin\n\u002F\u002F src\u002Ftest\u002Fkotlin\u002Fcom\u002Fexample\u002FAddTest.kt\nfun add(a: Int, b: Int): Int = TODO() \u002F\u002F stub\n\nclass AddTest : FunSpec({\n    test(\"adds two numbers\") { \u002F\u002F RED\n        add(2, 3) shouldBe 5\n    }\n})\n\n\u002F\u002F src\u002Fmain\u002Fkotlin\u002Fcom\u002Fexample\u002FMath.kt\nfun add(a: Int, b: Int): Int = a + b \u002F\u002F GREEN\n\n\u002F\u002F REFACTOR: simplify\u002Frename once tests pass\n```\n\n## Code Examples\n\n### Basic Unit Test (Kotest FunSpec)\n\n```kotlin\nimport io.kotest.core.spec.style.FunSpec\nimport io.kotest.matchers.shouldBe\n\nclass CalculatorTest : FunSpec({\n    test(\"adds two numbers\") {\n        Calculator.add(2, 3) shouldBe 5\n    }\n\n    test(\"handles negative numbers\") {\n        Calculator.add(-1, 1) shouldBe 0\n    }\n})\n```\n\n### DescribeSpec (BDD Style)\n\n```kotlin\nimport io.kotest.core.spec.style.DescribeSpec\nimport io.kotest.matchers.shouldBe\nimport io.kotest.matchers.shouldNotBe\n\nclass UserStoreTest : DescribeSpec({\n    lateinit var store: UserStore\n\n    beforeTest {\n        store = UserStore()\n        store.seed(listOf(User(\"alice\"), User(\"bob\")))\n    }\n\n    describe(\"find user\") {\n        it(\"should return existing user\") {\n            val user = store.find(\"alice\")\n            user shouldNotBe null\n            user?.name shouldBe \"alice\"\n        }\n\n        it(\"should return null for missing user\") {\n            store.find(\"charlie\") shouldBe null\n        }\n    }\n})\n```\n\n### Mocking (MockK)\n\n```kotlin\nimport io.mockk.*\nimport io.kotest.core.spec.style.FunSpec\nimport io.kotest.matchers.shouldBe\n\ninterface Notifier {\n    fun send(message: String)\n}\n\nclass Service(private val notifier: Notifier) {\n    fun publish(message: String) = notifier.send(message)\n}\n\nclass ServiceTest : FunSpec({\n    test(\"sends notifications\") {\n        val notifier = mockk\u003CNotifier>()\n        every { notifier.send(\"hello\") } just Runs\n        val service = Service(notifier)\n\n        service.publish(\"hello\")\n\n        verify(exactly = 1) { notifier.send(\"hello\") }\n    }\n})\n```\n\n### Coroutine Test\n\n```kotlin\nimport io.kotest.core.spec.style.FunSpec\nimport io.kotest.matchers.shouldBe\nimport io.kotest.assertions.timing.eventually\nimport kotlin.time.Duration.Companion.seconds\n\nclass ApiTest : FunSpec({\n    test(\"fetches user data\") {\n        eventually(5.seconds) {\n            val user = fetchUser(\"1\")\n            user.name shouldBe \"alice\"\n        }\n    }\n})\n```\n\n### Property-Based Testing (Kotest)\n\n```kotlin\nimport io.kotest.core.spec.style.FunSpec\nimport io.kotest.property.Arb\nimport io.kotest.property.arbitrary.int\nimport io.kotest.property.forAll\nimport io.kotest.matchers.shouldBe\n\nclass MathPropertyTest : FunSpec({\n    test(\"add is commutative\") {\n        forAll(Arb.int(), Arb.int()) { a, b ->\n            Math.add(a, b) == Math.add(b, a)\n        }\n    }\n})\n```\n\n### StringSpec (Simple Tests)\n\n```kotlin\nimport io.kotest.core.spec.style.StringSpec\nimport io.kotest.matchers.string.shouldContain\n\nclass ValidationTest : StringSpec({\n    \"should reject negative age\" {\n        shouldThrow\u003CIllegalArgumentException> {\n            Validator.validateAge(-1)\n        }.message shouldContain \"non-negative\"\n    }\n})\n```\n\n### Data-Driven Test\n\n```kotlin\nimport io.kotest.core.spec.style.FunSpec\nimport io.kotest.matchers.shouldBe\nimport io.kotest.datatest.withData\n\nclass MathParamTest : FunSpec({\n    context(\"add function\") {\n        withData(\n            nameFn = { \"${it.a} + ${it.b} = ${it.expected}\" },\n            TestCase(1, 2, 3),\n            TestCase(-1, 1, 0),\n            TestCase(0, 0, 0),\n            TestCase(100, 200, 300),\n        ) { (a, b, expected) ->\n            Math.add(a, b) shouldBe expected\n        }\n    }\n}) {\n    data class TestCase(val a: Int, val b: Int, val expected: Int)\n}\n```\n\n## Build Configuration (Gradle)\n\n```kotlin\n\u002F\u002F build.gradle.kts\nplugins {\n    kotlin(\"jvm\") version \"2.0.0\"\n}\n\ndependencies {\n    testImplementation(\"io.kotest:kotest-runner-junit5:5.9.0\")\n    testImplementation(\"io.kotest:kotest-assertions-core:5.9.0\")\n    testImplementation(\"io.kotest:kotest-property:5.9.0\")\n    testImplementation(\"io.kotest:kotest-framework-datatest:5.9.0\")\n    testImplementation(\"io.mockk:mockk:1.13.12\")\n    testImplementation(\"org.jetbrains.kotlinx:kotlinx-coroutines-test:1.10.0\")\n}\n\ntasks.test {\n    useJUnitPlatform()\n    testLogging {\n        events(\"passed\", \"skipped\", \"failed\")\n    }\n}\n```\n\n## Running Tests\n\n```bash\n.\u002Fgradlew test                         # all tests\n.\u002Fgradlew test --tests \"*CalculatorTest*\"\n.\u002Fgradlew test --info                  # verbose output\n.\u002Fgradlew test --continuous            # watch mode\n.\u002Fgradlew test -Dkotest.tags=\"Integration\"\n```\n\n## Coverage\n\n```kotlin\n\u002F\u002F build.gradle.kts — JaCoCo\nplugins {\n    id(\"jacoco\")\n}\n\ntasks.jacocoTestReport {\n    dependsOn(tasks.test)\n    reports {\n        xml.required.set(true)\n        html.required.set(true)\n    }\n}\n```\n\n```bash\n.\u002Fgradlew test jacocoTestReport\n```\n\n## CI\u002FCD Integration (GitHub Actions)\n\n```yaml\n# .github\u002Fworkflows\u002Ftest.yml\nname: Test\non: [push, pull_request]\njobs:\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-java@v4\n        with: { java-version: '21', distribution: 'temurin' }\n      - run: .\u002Fgradlew test jacocoTestReport\n      - uses: actions\u002Fupload-artifact@v4\n        if: always()\n        with: { name: test-results, path: '**\u002Ftest-results\u002F**\u002F*.xml' }\n```\n\n## Flaky Tests Guardrails\n\n- Never use `Thread.sleep()` in coroutine tests; use `kotlinx.coroutines.test`.\n- Use `UnconfinedTestDispatcher` or `StandardTestDispatcher` for controlled coroutine scope.\n- Make temp files unique with `createTempFile()` \u002F `createTempDir()`.\n- Mock `kotlinx.datetime.Clock` for time-dependent code.\n\n## Test Case Design Patterns\n\nApply these systematic patterns before writing test code to ensure robust coverage beyond the happy path.\n\n### 1. Boundary Value Analysis\nTest at the edges of valid input domains: empty, zero, maximum, null, and just-outside valid ranges.\n\n```kotlin\n\u002F\u002F src\u002Ftest\u002Fkotlin\u002Fcom\u002Fexample\u002FValidatorTest.kt\nclass ValidatorTest : FunSpec({\n    context(\"input validation\") {\n        withData(\n            nameFn = { \"rejects ${it.name}\" },\n            TestCase(\"\", \"empty\"),\n            TestCase(\" \", \"whitespace\"),\n            TestCase(\"a\".repeat(10001), \"too long\")\n        ) { (input, _) ->\n            shouldThrow\u003CIllegalArgumentException> { validator.validate(input) }\n        }\n    }\n}) {\n    data class TestCase(val input: String, val name: String)\n}\n```\n\n### 2. Negative \u002F Error Case Testing\nVerify the system behaves correctly under invalid or unexpected conditions.\n\n```kotlin\nclass CalculatorTest : FunSpec({\n    test(\"throws on divide by zero\") {\n        shouldThrow\u003CArithmeticException> { calculator.divide(10, 0) }\n    }\n})\n```\n\n### 3. State-Based Testing\nFor objects with internal state, verify transitions between states are correct and irreversible where expected.\n\n```kotlin\nclass ConnectionTest : FunSpec({\n    test(\"state transitions are correct\") {\n        val conn = Connection()\n        conn.state shouldBe State.CLOSED\n        conn.open()\n        conn.state shouldBe State.OPEN\n        conn.close()\n        conn.state shouldBe State.CLOSED\n        \u002F\u002F Idempotency\n        conn.close()\n        conn.state shouldBe State.CLOSED\n    }\n})\n```\n\n## Common Test Smells to Avoid\n\n- **Assertion Roulette**: Many assertions without descriptive messages, making failure diagnosis ambiguous. *Fix: Use Kotest `\"value\" shouldBe expected` with descriptive test names.*\n- **Happy Path Bias**: Only testing successful scenarios, leaving error paths uncovered. *Fix: Test `null` values, exceptions with `shouldThrow\u003C>`, edge inputs.*\n- **Mock Overdose**: Too many mocks hiding integration issues or coupling tests to implementation. *Fix: Mock only at architectural boundaries (repositories, services); use `relaxed = true` only when needed.*\n- **The Free Ride**: Tests that execute code but assert nothing meaningful. *Fix: Every test must have at least one specific, falsifiable assertion.*\n- **Obscure Test**: Long test functions with no clear arrange\u002Fact\u002Fassert structure. *Fix: Follow AAA, choose a consistent spec style (FunSpec\u002FDescribeSpec), keep tests focused.*\n- **Flaky Test**: Non-deterministic results from coroutines, time, or shared state. *Fix: Use `runTest { }` with `UnconfinedTestDispatcher`, `clearAllMocks()` between tests.*\n\n## Best Practices\n\n### DO\n\n- Use Kotest style specs that match your team's preference (FunSpec for simple, DescribeSpec for BDD)\n- Use `shouldBe`, `shouldNotBe`, `shouldThrow` from Kotest matchers\n- Use coroutine test dispatchers instead of `runBlocking`\n- Use property-based testing for invariant validation\n- Use `withData` for readable parametrized tests\n\n### DON'T\n\n- Don't use `Thread.sleep()` for synchronization in coroutine tests\n- Don't mix JUnit 4 and Kotest annotations\n- Don't mock value objects or data classes\n- Don't use `runBlocking` in tests — use coroutine test dispatchers\n- Don't over-use `io.mockk.every` for simple return values\n\n### Common Pitfalls\n\n- **Coroutine leaks** → Always use `runTest` from `kotlinx-coroutines-test`.\n- **Flaky time-based tests** → Use `TestDispatcher` with `advanceTimeBy()`.\n- **MockK leaks** → Use `clearAllMocks()` in `afterProject` or `afterTest`.\n- **Android instrumentation** → Use `@MediumTest` \u002F `@LargeTest` annotations.\n\n### Android Testing (ActivityScenario + Espresso)\n\n```kotlin\n\u002F\u002F app\u002Fsrc\u002FandroidTest\u002Fkotlin\u002FLoginActivityTest.kt\nimport androidx.test.ext.junit.runners.AndroidJUnit4\nimport androidx.test.core.app.ActivityScenario\nimport androidx.test.espresso.Espresso.onView\nimport androidx.test.espresso.action.ViewActions.*\nimport androidx.test.espresso.assertion.ViewAssertions.matches\nimport androidx.test.espresso.matcher.ViewMatchers.*\nimport org.junit.Test\nimport org.junit.runner.RunWith\n\n@RunWith(AndroidJUnit4::class)\nclass LoginActivityTest {\n\n    @Test\n    fun testSuccessfulLogin() {\n        val scenario = ActivityScenario.launch(LoginActivity::class.java)\n\n        onView(withId(R.id.emailInput))\n            .perform(typeText(\"user@example.com\"))\n        onView(withId(R.id.passwordInput))\n            .perform(typeText(\"password123\"))\n        onView(withId(R.id.loginButton))\n            .perform(click())\n        onView(withId(R.id.welcomeText))\n            .check(matches(withText(\"Welcome!\")))\n\n        scenario.close()\n    }\n}\n```\n\n> **build.gradle.kts dependencies**: Add `androidx.test:core-ktx:1.6.x`, `androidx.test.espresso:espresso-core:3.6.x`, `androidx.test:runner:1.6.x` for androidTest source set.\n\n## Mutation Testing (PIT)\n\n```kotlin\n\u002F\u002F build.gradle.kts\nplugins {\n    id(\"info.solidsoft.pitest\") version \"1.15.0\"\n}\n\npitest {\n    targetClasses.set(listOf(\"com.example.*\"))\n    mutators.set(listOf(\"STRONGER\"))\n    outputFormats.set(listOf(\"HTML\"))\n}\n```\n\n```bash\n.\u002Fgradlew pitest\n# Report: build\u002Freports\u002Fpitest\u002Findex.html\n```\n\n> Mutation testing verifies tests catch bugs by introducing code mutations (e.g., `+` → `-`). **Target ≥80% mutation score** for business logic.\n\n## Alternatives\n\n- **JUnit 5 + MockK**: Simpler setup, JUnit-compatible, good for mixed Java\u002FKotlin projects.\n- **Spek**: Structure-based testing with `@Describe` \u002F `@It` annotations.\n- **Turbine**: Kotlin Flow testing.\n",{"name":5,"metadata":24,"description":27,"compatibility":28},{"author":25,"source":26},"github-spec-kit","templates\u002Fpassive-skills\u002Fkotlin-testing\u002FSKILL.md","Use ONLY when user explicitly requests Kotlin test code, Kotest\u002FMockK configuration, test failure diagnosis, or coverage improvement for Kotlin projects.\nTriggers: \"write test kotlin\", \"kotest\", \"mockk\", \"coroutine test\", \"kotlin coverage\", \"runTest\", \"property testing kotlin\", \"ActivityScenario\".\nDo NOT activate for: general Kotlin coding without test context, Gradle build errors, Kotlin multiplatform setup, or Android UI implementation without test needs. ","Requires spec-kit project structure with .specify\u002F directory","main","021f5cbe02157229460a577e9a585f2da6d78cb0",".codex\u002Fskills\u002Fkotlin-testing","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck","https:\u002F\u002Fgithub.com\u002Fchenziyang110","2026-08-07 18:10:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add chenziyang110\u002Flaunchdeck --skill kotlin-testing",{"tool":41,"command":42},"bunx","bunx skills add chenziyang110\u002Flaunchdeck --skill kotlin-testing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add chenziyang110\u002Flaunchdeck --skill kotlin-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fkotlin-testing\u002FSKILL.md",true,[],[50,57,63,69,76,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7875F3HQ1GF5F6BR36KY3JE","launchdeck-agent","Codex host adapter contract fixture for Launchdeck.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fagent-hosts\u002Fcodex\u002Fskill\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7875DV2DQR33K1NFJHKAMZP","Claude host adapter contract fixture for Launchdeck.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fagent-hosts\u002Fclaude\u002Fskill\u002FSKILL.md",[],[],{"skillNo":64,"name":52,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M78759JQ7A6FQ8KDQTNYS3X9","Use this skill aggressively for local project lifecycle operations even when the user does not mention Launchdeck: start this project, run the dev server, dev, build, test, restart service, stop service, show logs, inspect ports, port is occupied, clean cache; and when the user explicitly asks to configure this local project for Launchdeck or create or generate a project-adapted `.launchdeck.yml`, including 为这个项目生成 Launchdeck 配置. Do not use for ordinary code edits, docs-only work, general explanations, API design discussion, or production deployment unless the user also asks to operate or configure a local project or service.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Fagent\u002Finstaller-payload\u002Fskill\u002Flaunchdeck-agent\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M78753ZJQ7G2CZT1W1G8WRJV","zig-testing","Use ONLY when user explicitly requests Zig test code, built-in test runner configuration,\ntest failure diagnosis, or coverage for Zig projects.\n\nTriggers: \"write test zig\", \"zig test\", \"testing.allocator\", \"zig coverage\",\n\"comptime test\", \"zig expectError\", \"zig snapshot test\", \"zig fuzz\".\n\nDo NOT activate for: general Zig coding without test context, build.zig configuration\nfor non-test targets, Zig compiler errors, or Zig build system setup.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fzig-testing\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M78750JXY4Z5D5W1EX3PQ31Z","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7874X2T83EQQFRCEY5SJJVC","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fverification-before-completion\u002FSKILL.md",[],[]]