[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M786XFASM2PY3MH1XMS7P5H7":3,"skill-same:01M786XFASM2PY3MH1XMS7P5H7":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},"01M786XFASM2PY3MH1XMS7P5H7","swift-testing",null,"Use ONLY when user explicitly requests Swift test code, XCTest\u002FSwift Testing configuration, test failure diagnosis, or coverage improvement for Swift\u002FApple-platform projects.\nTriggers: \"write test swift\", \"XCTest\", \"swift testing\", \"@Test macro\", \"xcode test\", \"swift coverage\", \"XCUITest\", \"Quick Nimble\".\nDo NOT activate for: general Swift coding without test context, SPM\u002FPackage.swift setup, Xcode project configuration, or SwiftUI\u002FUIKit 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\u002Fswift-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"swift-testing\"\ndescription: \"Use ONLY when user explicitly requests Swift test code, XCTest\u002FSwift Testing configuration,\ntest failure diagnosis, or coverage improvement for Swift\u002FApple-platform projects.\n\nTriggers: \\\"write test swift\\\", \\\"XCTest\\\", \\\"swift testing\\\", \\\"@Test macro\\\",\n\\\"xcode test\\\", \\\"swift coverage\\\", \\\"XCUITest\\\", \\\"Quick Nimble\\\".\n\nDo NOT activate for: general Swift coding without test context, SPM\u002FPackage.swift\nsetup, Xcode project configuration, or SwiftUI\u002FUIKit 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\u002Fswift-testing\u002FSKILL.md\"\n---\n\n\n# Swift Testing (Agent Skill)\n\nAgent-focused testing workflow for modern Swift using XCTest, the official Apple test framework for iOS\u002FmacOS\u002FwatchOS\u002FtvOS and server-side Swift.\n\n## When to Use\n\n- Writing new Swift tests or fixing existing tests\n- Designing unit\u002Fintegration test coverage for Swift components\n- Adding test coverage, CI gating, or regression protection\n- Configuring XCTest workflows for consistent execution\n- Investigating test failures or flaky behavior\n- Testing iOS\u002FmacOS UI, REST APIs, or Swift Packages\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-Swift 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** (tight coupling to UIKit lifecycle, hard-coded UserDefaults, no protocol abstractions)\n- **No test target** is configured in Package.swift or Xcode project\n- The request is **ambiguous**: \"test my app\" or \"add tests\" without specifying files or types\n- A **required test dependency** (XCTest, Swift Testing) is not configured in the test target\n- The test would require **secrets, real credentials, or production API access**\n\n## Core Concepts\n\n- **TDD loop**: red → green → refactor (tests first, minimal fix, then cleanups).\n- **XCTest**: `XCTestCase` subclasses with `testXxx` methods.\n- **Async testing**: `XCTestExpectation` for async code; async\u002Fawait natively supported.\n- **Test layout**: `Tests\u002F` directory at package root, `Sources\u002F` for production code.\n- **UI testing**: XCUITest for iOS\u002FmacOS UI automation.\n- **CI signal**: `xcodebuild test` or `swift test --parallel`.\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 Swift version (5.9+) and test framework (XCTest or Swift Testing).\n2. Check for existing test files (`Tests\u002F`, `*Tests.swift`) to infer naming conventions and style.\n3. Analyze the code under test: identify public API surface, `async\u002Fawait` usage, `@MainActor` requirements, and UI boundaries.\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 utilities**: unit tests only, no mocks. Use `XCTestCase` with `XCTAssertEqual` or Swift Testing `@Test`.\n- **External dependencies (network, database)**: use protocol-based dependency injection with manual mock structs.\n- **Async code**: use `async throws` test methods (Swift 5.5+) or `XCTestExpectation` for legacy callbacks.\n- **UI tests**: use XCUITest for iOS\u002FmacOS automation; reset app state between tests.\n- **Modern projects (Swift 6+)**: prefer Swift Testing framework (`@Test`, `@Suite`, `@Arguments`) over XCTest.\n\n### Decision Tree (Complex Scenarios)\n\n```text\nQ1: External I\u002FO (network, database, filesystem)?\n  → Yes → Q2\n  → No  → Pure unit test, no mocks needed\n\nQ2: Mockable via protocol?\n  → Yes → Protocol-based manual mock struct\n  → No  → Q3\n\nQ3: Async (async\u002Fawait, Combine, callbacks)?\n  → Yes → async throws test \u002F XCTestExpectation\n  → No  → Synchronous test sufficient\n\nQ4: UI interaction (iOS\u002FmacOS)?\n  → Yes → XCUITest with accessibility identifiers\n  → No  → Q5\n\nQ5: Swift 6+ \u002F greenfield project?\n  → Yes → Swift Testing (@Test, @Suite, @Arguments)\n  → No  → XCTest (XCTAssertEqual, XCTestCase)\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 arrays, `nil`, `0`, `Int.max`, empty strings, `Date.distantPast`.\n3. **Error cases**: thrown errors (`throws` \u002F `XCTAssertThrowsError`), `nil` unwrap failures, `Result.failure`.\n4. **Concurrency**: `@MainActor` isolation, `Task` cancellation, `Actor` reentrancy.\n\n### Phase 4: Code Generation\nOutput tests in this exact structure:\n```\n#### Test Strategy Summary\n- [ ] Scope: Unit \u002F Integration \u002F UI\n- [ ] Framework: XCTest (or Swift Testing for Swift 6+)\n- [ ] Mocking: Yes\u002FNo — protocol-based manual mocks\n- [ ] Edge cases covered: \u003Clist>\n\n#### Generated Test Code\n\u003Cfile_path>\n\u003Ccode>\n\n#### Running Commands\n```bash\nswift test --filter \"ClassName\"\nswift test --parallel\nxcodebuild test -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 16'\n```\n\n#### Coverage Impact (if applicable)\n- Estimated coverage change: \u003CX%>\n- Command to verify: `swift test --enable-code-coverage`\n```\n\n### Phase 5: Verification Checklist\nBefore completing, verify:\n- [ ] Tests compile and pass (`swift test`).\n- [ ] Each test has exactly one logical assertion focus.\n- [ ] Shared mutable state is reset in `setUp()` \u002F `tearDown()`.\n- [ ] No `sleep()` used for synchronization (use `XCTestExpectation` or `async\u002Fawait`).\n- [ ] Flaky test guardrails applied (unique test data, protocol-based DI, `--parallel` stress test).\n\n## TDD Workflow\n\nFollow the RED → GREEN → REFACTOR loop:\n\n```swift\n\u002F\u002F Tests\u002FAddTests.swift\nfunc add(_ a: Int, _ b: Int) -> Int { fatalError() } \u002F\u002F stub\n\nfinal class AddTests: XCTestCase {\n    func testAddsTwoNumbers() { \u002F\u002F RED\n        XCTAssertEqual(add(2, 3), 5)\n    }\n}\n\n\u002F\u002F Sources\u002FMyLib\u002FMath.swift\nfunc 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\n\n```swift\nimport XCTest\n\nfinal class CalculatorTests: XCTestCase {\n    func testAddsTwoNumbers() {\n        XCTAssertEqual(Calculator.add(2, 3), 5)\n    }\n\n    func testHandlesNegative() {\n        XCTAssertEqual(Calculator.add(-1, 1), 0)\n    }\n}\n```\n\n### Setup \u002F Teardown\n\n```swift\nfinal class UserStoreTests: XCTestCase {\n    var store: UserStore!\n\n    override func setUp() {\n        super.setUp()\n        store = UserStore()\n        store.seed([User(name: \"alice\"), User(name: \"bob\")])\n    }\n\n    override func tearDown() {\n        store = nil\n        super.tearDown()\n    }\n\n    func testFindsExistingUser() {\n        let user = store.find(\"alice\")\n        XCTAssertNotNil(user)\n        XCTAssertEqual(user?.name, \"alice\")\n    }\n}\n```\n\n### Mocking (Manual \u002F Protocol)\n\n```swift\nprotocol Notifier {\n    func send(_ message: String)\n}\n\nfinal class MockNotifier: Notifier {\n    var sentMessages: [String] = []\n\n    func send(_ message: String) {\n        sentMessages.append(message)\n    }\n}\n\nfinal class ServiceTests: XCTestCase {\n    func testSendsNotification() {\n        let notifier = MockNotifier()\n        let service = Service(notifier: notifier)\n\n        service.publish(\"hello\")\n\n        XCTAssertEqual(notifier.sentMessages, [\"hello\"])\n    }\n}\n```\n\n### Async Test (XCTestExpectation)\n\n```swift\nfinal class ApiTests: XCTestCase {\n    func testFetchesUserData() {\n        let expectation = XCTestExpectation(description: \"fetch user\")\n\n        fetchUser(id: \"1\") { user in\n            XCTAssertEqual(user.name, \"alice\")\n            expectation.fulfill()\n        }\n\n        wait(for: [expectation], timeout: 2.0)\n    }\n}\n```\n\n### Async\u002FAwait Test (Swift 5.5+)\n\n```swift\nfinal class ApiTests: XCTestCase {\n    func testFetchesUserData() async throws {\n        let user = try await fetchUser(id: \"1\")\n        XCTAssertEqual(user.name, \"alice\")\n    }\n\n    func testHandlesError() async {\n        await XCTExpectFailure {\n            try? await fetchUser(id: \"invalid\")\n        }\n    }\n}\n```\n\n### Performance Test\n\n```swift\nfinal class PerformanceTests: XCTestCase {\n    func testSortingPerformance() {\n        let array = (0..\u003C1000).shuffled()\n        measure {\n            _ = array.sorted()\n        }\n        \u002F\u002F baseline: ~0.001s (adjust per project)\n    }\n}\n```\n\n### Parametrized (Manual Loop)\n\n```swift\nfinal class MathTests: XCTestCase {\n    func testAdd() {\n        let cases: [(a: Int, b: Int, expected: Int)] = [\n            (1, 2, 3),\n            (-1, 1, 0),\n            (0, 0, 0),\n            (100, 200, 300),\n        ]\n        for (a, b, expected) in cases {\n            XCTAssertEqual(Calculator.add(a, b), expected)\n        }\n    }\n}\n```\n\n### UI Test (XCUITest)\n\n```swift\nfinal class MyAppUITests: XCTestCase {\n    let app = XCUIApplication()\n\n    override func setUp() {\n        continueAfterFailure = false\n        app.launch()\n    }\n\n    func testLoginButtonExists() {\n        let loginButton = app.buttons[\"Login\"]\n        XCTAssertTrue(loginButton.exists)\n    }\n\n    func testLoginFlow() {\n        app.textFields[\"Email\"].tap()\n        app.textFields[\"Email\"].typeText(\"user@example.com\")\n        app.buttons[\"Login\"].tap()\n        XCTAssertTrue(app.staticTexts[\"Welcome\"].waitForExistence(timeout: 5))\n    }\n}\n```\n\n## Swift Testing Framework (Swift 6+)\n\nApple's modern testing framework is the recommended choice for new Swift 6+ projects. It uses macros for declarative test definition and integrates natively with Swift Package Manager and Xcode 16+.\n\n### Basic Test\n\n```swift\nimport Testing\n\n@Test(\"Adds two numbers\")\nfunc addTest() {\n    #expect(add(2, 3) == 5)\n}\n```\n\n### Parametrized Test\n\n```swift\nimport Testing\n\n@Test(\"Parametrized addition\",\n    arguments: [(1, 2, 3), (-1, 1, 0), (0, 0, 0), (100, 200, 300)])\nfunc addParametrized(a: Int, b: Int, expected: Int) {\n    #expect(add(a, b) == expected)\n}\n```\n\n### Async Test\n\n```swift\nimport Testing\n\n@Test(\"Fetches user data\")\nfunc fetchUser() async throws {\n    let user = try await fetchUser(id: \"1\")\n    #expect(user.name == \"alice\")\n}\n```\n\n### Tagged Tests\n\n```swift\nimport Testing\n\n@Test(.tags(.integration))\nfunc databaseQuery() async throws {\n    \u002F\u002F Runs only when explicitly requested via tag filter\n}\n```\n\n### Running Swift Testing\n\n```bash\nswift test                           # discovers @Test automatically\nswift test --filter \"addTest\"\nswift test --skip \"integration\"      # skip tags\n```\n\n### Migrating from XCTest\n\n| XCTest | Swift Testing |\n|--------|---------------|\n| `XCTestCase` | `@Suite` |\n| `func testXxx()` | `@Test` |\n| `XCTAssertEqual(a, b)` | `#expect(a == b)` |\n| `XCTAssertThrowsError` | `#expect(throws: ...) { ... }` |\n| `setUp()` | `init()` on `@Suite` |\n| `measure { }` | `@Test(.enabled(if: ...))` + manual timing |\n\n## Package.swift Quickstart\n\n```swift\n\u002F\u002F swift-tools-version: 5.9\nimport PackageDescription\n\nlet package = Package(\n    name: \"MyLibrary\",\n    products: [\n        .library(name: \"MyLibrary\", targets: [\"MyLibrary\"]),\n    ],\n    targets: [\n        .target(name: \"MyLibrary\"),\n        .testTarget(\n            name: \"MyLibraryTests\",\n            dependencies: [\"MyLibrary\"]\n        ),\n    ]\n)\n```\n\n## Running Tests\n\n```bash\nswift test                          # run all tests\nswift test --parallel               # parallel execution\nswift test --filter \"AddTests\"      # run specific test class\nswift test --filter \"testAdd\"       # run tests matching pattern\nswift test --enable-code-coverage   # with coverage\n\nxcodebuild test \\\n    -scheme MyApp \\\n    -destination 'platform=iOS Simulator,name=iPhone 16'\n```\n\n## Coverage\n\n```bash\nswift test --enable-code-coverage\nllvm-cov report \\\n    .build\u002Fdebug\u002FMyLibraryPackageTests.xctest\u002FContents\u002FMacOS\u002FMyLibraryPackageTests \\\n    --instr-profile=.build\u002Fdebug\u002Fcodecov\u002Fdefault.profdata\n```\n\n```bash\n# Using xccov (Xcode)\nxcodebuild -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 16' \\\n    -enableCodeCoverage YES test\nxcrun xccov view --report --json DerivedData\u002F**\u002FLogs\u002FTest\u002F*.xcresult\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: macos-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - run: swift test --enable-code-coverage\n      - run: xcrun llvm-cov export -format=lcov .build\u002Fdebug\u002F*.xctest -instr-profile .build\u002Fdebug\u002Fcodecov\u002Fdefault.profdata > coverage.lcov\n```\n\n## Flaky Tests Guardrails\n\n- Never use `sleep()` for synchronization; use `XCTestExpectation`.\n- Make test data unique per test with UUID-based identifiers.\n- Mock network calls using protocol-based dependency injection.\n- Use `continueAfterFailure = false` carefully — prefer testing one failure at a time.\n- Reset app state between UI tests by launching fresh.\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, nil, and just-outside valid ranges.\n\n```swift\n\u002F\u002F Tests\u002FValidatorTests.swift\nfinal class ValidatorTests: XCTestCase {\n    func testRejectsInvalidInput() {\n        XCTAssertThrowsError(try validator.validate(\"\")) { error in\n            XCTAssertTrue(error is ValidationError)\n        }\n        let longInput = String(repeating: \"a\", count: 10001)\n        XCTAssertThrowsError(try validator.validate(longInput))\n    }\n}\n```\n\n### 2. Negative \u002F Error Case Testing\nVerify the system behaves correctly under invalid or unexpected conditions.\n\n```swift\n\u002F\u002F Tests\u002FCalculatorTests.swift\nfinal class CalculatorTests: XCTestCase {\n    func testThrowsOnDivideByZero() {\n        XCTAssertThrowsError(try 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```swift\n\u002F\u002F Tests\u002FConnectionTests.swift\nfinal class ConnectionTests: XCTestCase {\n    func testStateTransitions() {\n        let conn = Connection()\n        XCTAssertEqual(conn.state, .closed)\n        conn.open()\n        XCTAssertEqual(conn.state, .open)\n        conn.close()\n        XCTAssertEqual(conn.state, .closed)\n        \u002F\u002F Idempotency\n        conn.close()\n        XCTAssertEqual(conn.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 `XCTAssertEqual(actual, expected, \"descriptive message\")` or Swift Testing `#expect(actual == expected)`.*\n- **Happy Path Bias**: Only testing successful scenarios, leaving error paths uncovered. *Fix: Test `nil` values with `XCTAssertNil`\u002F`XCTAssertNotNil`, `XCTAssertThrowsError` for exceptions.*\n- **Mock Overdose**: Too many protocol mocks hiding integration issues. *Fix: Mock only at service boundaries; prefer real implementations for value types.*\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 `XCTestCase` methods with no clear setup\u002Fverify structure. *Fix: Follow AAA, use `setUpWithError()`\u002F`tearDownWithError()`, keep test methods focused.*\n- **Flaky Test**: Non-deterministic results from async, UI, or test order. *Fix: Use `XCTestExpectation` with timeouts, `continueAfterFailure = false`, test isolation.*\n\n## Best Practices\n\n### DO\n\n- Use descriptive `testXxx` method names (e.g., `testAdd_WithPositiveNumbers_ReturnsSum`)\n- Use `XCTestExpectation` + `wait(for:timeout:)` for async code\n- Use `throws` functions to avoid `try?` in tests\n- Use `#fileID` \u002F `#line` for helper assertion functions\n- Separate unit, integration, and UI tests into separate targets\n\n### DON'T\n\n- Don't use `sleep()` for synchronization\n- Don't depend on real network or time in unit tests\n- Don't share mutable state between test methods\n- Don't test private methods directly — test through public API\n- Don't write UI tests that depend on specific screen sizes without layout checks\n\n### Common Pitfalls\n\n- **Flaky async tests** → Always use `XCTestExpectation` with timeout.\n- **Shared state** → Reset in `setUp()` \u002F `tearDown()`.\n- **Hardcoded delays** → Use `waitForExistence(timeout:)` in UI tests.\n- **Network in unit tests** → Mock `URLProtocol` or use protocol-based DI.\n- **Slow UI tests** → Mark slow tests with `-[XCUIApplication launch]` per test.\n- **Missing coverage gates** → Add `--enable-code-coverage` in CI.\n\n## Optional: Swift Testing Framework (Swift 6+)\n\nThe new Swift Testing framework (available in Swift 6+) is the modern alternative:\n\n```swift\nimport Testing\n\n@Test(\"Adds two numbers\")\nfunc addTest() {\n    #expect(add(2, 3) == 5)\n}\n\n@Test(\"Parametrized addition\",\n    arguments: [(1, 2, 3), (-1, 1, 0), (0, 0, 0)])\nfunc addParametrized(a: Int, b: Int, expected: Int) {\n    #expect(add(a, b) == expected)\n}\n```\n\n## Alternatives\n\n- **Quick + Nimble** (v7.x): BDD-style testing with expressive matchers.\n- **Swift Testing**: Apple's new test framework (Swift 6+), modern macro-based API.\n","# Swift Testing (Agent Skill)\n\nAgent-focused testing workflow for modern Swift using XCTest, the official Apple test framework for iOS\u002FmacOS\u002FwatchOS\u002FtvOS and server-side Swift.\n\n## When to Use\n\n- Writing new Swift tests or fixing existing tests\n- Designing unit\u002Fintegration test coverage for Swift components\n- Adding test coverage, CI gating, or regression protection\n- Configuring XCTest workflows for consistent execution\n- Investigating test failures or flaky behavior\n- Testing iOS\u002FmacOS UI, REST APIs, or Swift Packages\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-Swift 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** (tight coupling to UIKit lifecycle, hard-coded UserDefaults, no protocol abstractions)\n- **No test target** is configured in Package.swift or Xcode project\n- The request is **ambiguous**: \"test my app\" or \"add tests\" without specifying files or types\n- A **required test dependency** (XCTest, Swift Testing) is not configured in the test target\n- The test would require **secrets, real credentials, or production API access**\n\n## Core Concepts\n\n- **TDD loop**: red → green → refactor (tests first, minimal fix, then cleanups).\n- **XCTest**: `XCTestCase` subclasses with `testXxx` methods.\n- **Async testing**: `XCTestExpectation` for async code; async\u002Fawait natively supported.\n- **Test layout**: `Tests\u002F` directory at package root, `Sources\u002F` for production code.\n- **UI testing**: XCUITest for iOS\u002FmacOS UI automation.\n- **CI signal**: `xcodebuild test` or `swift test --parallel`.\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 Swift version (5.9+) and test framework (XCTest or Swift Testing).\n2. Check for existing test files (`Tests\u002F`, `*Tests.swift`) to infer naming conventions and style.\n3. Analyze the code under test: identify public API surface, `async\u002Fawait` usage, `@MainActor` requirements, and UI boundaries.\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 utilities**: unit tests only, no mocks. Use `XCTestCase` with `XCTAssertEqual` or Swift Testing `@Test`.\n- **External dependencies (network, database)**: use protocol-based dependency injection with manual mock structs.\n- **Async code**: use `async throws` test methods (Swift 5.5+) or `XCTestExpectation` for legacy callbacks.\n- **UI tests**: use XCUITest for iOS\u002FmacOS automation; reset app state between tests.\n- **Modern projects (Swift 6+)**: prefer Swift Testing framework (`@Test`, `@Suite`, `@Arguments`) over XCTest.\n\n### Decision Tree (Complex Scenarios)\n\n```text\nQ1: External I\u002FO (network, database, filesystem)?\n  → Yes → Q2\n  → No  → Pure unit test, no mocks needed\n\nQ2: Mockable via protocol?\n  → Yes → Protocol-based manual mock struct\n  → No  → Q3\n\nQ3: Async (async\u002Fawait, Combine, callbacks)?\n  → Yes → async throws test \u002F XCTestExpectation\n  → No  → Synchronous test sufficient\n\nQ4: UI interaction (iOS\u002FmacOS)?\n  → Yes → XCUITest with accessibility identifiers\n  → No  → Q5\n\nQ5: Swift 6+ \u002F greenfield project?\n  → Yes → Swift Testing (@Test, @Suite, @Arguments)\n  → No  → XCTest (XCTAssertEqual, XCTestCase)\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 arrays, `nil`, `0`, `Int.max`, empty strings, `Date.distantPast`.\n3. **Error cases**: thrown errors (`throws` \u002F `XCTAssertThrowsError`), `nil` unwrap failures, `Result.failure`.\n4. **Concurrency**: `@MainActor` isolation, `Task` cancellation, `Actor` reentrancy.\n\n### Phase 4: Code Generation\nOutput tests in this exact structure:\n```\n#### Test Strategy Summary\n- [ ] Scope: Unit \u002F Integration \u002F UI\n- [ ] Framework: XCTest (or Swift Testing for Swift 6+)\n- [ ] Mocking: Yes\u002FNo — protocol-based manual mocks\n- [ ] Edge cases covered: \u003Clist>\n\n#### Generated Test Code\n\u003Cfile_path>\n\u003Ccode>\n\n#### Running Commands\n```bash\nswift test --filter \"ClassName\"\nswift test --parallel\nxcodebuild test -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 16'\n```\n\n#### Coverage Impact (if applicable)\n- Estimated coverage change: \u003CX%>\n- Command to verify: `swift test --enable-code-coverage`\n```\n\n### Phase 5: Verification Checklist\nBefore completing, verify:\n- [ ] Tests compile and pass (`swift test`).\n- [ ] Each test has exactly one logical assertion focus.\n- [ ] Shared mutable state is reset in `setUp()` \u002F `tearDown()`.\n- [ ] No `sleep()` used for synchronization (use `XCTestExpectation` or `async\u002Fawait`).\n- [ ] Flaky test guardrails applied (unique test data, protocol-based DI, `--parallel` stress test).\n\n## TDD Workflow\n\nFollow the RED → GREEN → REFACTOR loop:\n\n```swift\n\u002F\u002F Tests\u002FAddTests.swift\nfunc add(_ a: Int, _ b: Int) -> Int { fatalError() } \u002F\u002F stub\n\nfinal class AddTests: XCTestCase {\n    func testAddsTwoNumbers() { \u002F\u002F RED\n        XCTAssertEqual(add(2, 3), 5)\n    }\n}\n\n\u002F\u002F Sources\u002FMyLib\u002FMath.swift\nfunc 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\n\n```swift\nimport XCTest\n\nfinal class CalculatorTests: XCTestCase {\n    func testAddsTwoNumbers() {\n        XCTAssertEqual(Calculator.add(2, 3), 5)\n    }\n\n    func testHandlesNegative() {\n        XCTAssertEqual(Calculator.add(-1, 1), 0)\n    }\n}\n```\n\n### Setup \u002F Teardown\n\n```swift\nfinal class UserStoreTests: XCTestCase {\n    var store: UserStore!\n\n    override func setUp() {\n        super.setUp()\n        store = UserStore()\n        store.seed([User(name: \"alice\"), User(name: \"bob\")])\n    }\n\n    override func tearDown() {\n        store = nil\n        super.tearDown()\n    }\n\n    func testFindsExistingUser() {\n        let user = store.find(\"alice\")\n        XCTAssertNotNil(user)\n        XCTAssertEqual(user?.name, \"alice\")\n    }\n}\n```\n\n### Mocking (Manual \u002F Protocol)\n\n```swift\nprotocol Notifier {\n    func send(_ message: String)\n}\n\nfinal class MockNotifier: Notifier {\n    var sentMessages: [String] = []\n\n    func send(_ message: String) {\n        sentMessages.append(message)\n    }\n}\n\nfinal class ServiceTests: XCTestCase {\n    func testSendsNotification() {\n        let notifier = MockNotifier()\n        let service = Service(notifier: notifier)\n\n        service.publish(\"hello\")\n\n        XCTAssertEqual(notifier.sentMessages, [\"hello\"])\n    }\n}\n```\n\n### Async Test (XCTestExpectation)\n\n```swift\nfinal class ApiTests: XCTestCase {\n    func testFetchesUserData() {\n        let expectation = XCTestExpectation(description: \"fetch user\")\n\n        fetchUser(id: \"1\") { user in\n            XCTAssertEqual(user.name, \"alice\")\n            expectation.fulfill()\n        }\n\n        wait(for: [expectation], timeout: 2.0)\n    }\n}\n```\n\n### Async\u002FAwait Test (Swift 5.5+)\n\n```swift\nfinal class ApiTests: XCTestCase {\n    func testFetchesUserData() async throws {\n        let user = try await fetchUser(id: \"1\")\n        XCTAssertEqual(user.name, \"alice\")\n    }\n\n    func testHandlesError() async {\n        await XCTExpectFailure {\n            try? await fetchUser(id: \"invalid\")\n        }\n    }\n}\n```\n\n### Performance Test\n\n```swift\nfinal class PerformanceTests: XCTestCase {\n    func testSortingPerformance() {\n        let array = (0..\u003C1000).shuffled()\n        measure {\n            _ = array.sorted()\n        }\n        \u002F\u002F baseline: ~0.001s (adjust per project)\n    }\n}\n```\n\n### Parametrized (Manual Loop)\n\n```swift\nfinal class MathTests: XCTestCase {\n    func testAdd() {\n        let cases: [(a: Int, b: Int, expected: Int)] = [\n            (1, 2, 3),\n            (-1, 1, 0),\n            (0, 0, 0),\n            (100, 200, 300),\n        ]\n        for (a, b, expected) in cases {\n            XCTAssertEqual(Calculator.add(a, b), expected)\n        }\n    }\n}\n```\n\n### UI Test (XCUITest)\n\n```swift\nfinal class MyAppUITests: XCTestCase {\n    let app = XCUIApplication()\n\n    override func setUp() {\n        continueAfterFailure = false\n        app.launch()\n    }\n\n    func testLoginButtonExists() {\n        let loginButton = app.buttons[\"Login\"]\n        XCTAssertTrue(loginButton.exists)\n    }\n\n    func testLoginFlow() {\n        app.textFields[\"Email\"].tap()\n        app.textFields[\"Email\"].typeText(\"user@example.com\")\n        app.buttons[\"Login\"].tap()\n        XCTAssertTrue(app.staticTexts[\"Welcome\"].waitForExistence(timeout: 5))\n    }\n}\n```\n\n## Swift Testing Framework (Swift 6+)\n\nApple's modern testing framework is the recommended choice for new Swift 6+ projects. It uses macros for declarative test definition and integrates natively with Swift Package Manager and Xcode 16+.\n\n### Basic Test\n\n```swift\nimport Testing\n\n@Test(\"Adds two numbers\")\nfunc addTest() {\n    #expect(add(2, 3) == 5)\n}\n```\n\n### Parametrized Test\n\n```swift\nimport Testing\n\n@Test(\"Parametrized addition\",\n    arguments: [(1, 2, 3), (-1, 1, 0), (0, 0, 0), (100, 200, 300)])\nfunc addParametrized(a: Int, b: Int, expected: Int) {\n    #expect(add(a, b) == expected)\n}\n```\n\n### Async Test\n\n```swift\nimport Testing\n\n@Test(\"Fetches user data\")\nfunc fetchUser() async throws {\n    let user = try await fetchUser(id: \"1\")\n    #expect(user.name == \"alice\")\n}\n```\n\n### Tagged Tests\n\n```swift\nimport Testing\n\n@Test(.tags(.integration))\nfunc databaseQuery() async throws {\n    \u002F\u002F Runs only when explicitly requested via tag filter\n}\n```\n\n### Running Swift Testing\n\n```bash\nswift test                           # discovers @Test automatically\nswift test --filter \"addTest\"\nswift test --skip \"integration\"      # skip tags\n```\n\n### Migrating from XCTest\n\n| XCTest | Swift Testing |\n|--------|---------------|\n| `XCTestCase` | `@Suite` |\n| `func testXxx()` | `@Test` |\n| `XCTAssertEqual(a, b)` | `#expect(a == b)` |\n| `XCTAssertThrowsError` | `#expect(throws: ...) { ... }` |\n| `setUp()` | `init()` on `@Suite` |\n| `measure { }` | `@Test(.enabled(if: ...))` + manual timing |\n\n## Package.swift Quickstart\n\n```swift\n\u002F\u002F swift-tools-version: 5.9\nimport PackageDescription\n\nlet package = Package(\n    name: \"MyLibrary\",\n    products: [\n        .library(name: \"MyLibrary\", targets: [\"MyLibrary\"]),\n    ],\n    targets: [\n        .target(name: \"MyLibrary\"),\n        .testTarget(\n            name: \"MyLibraryTests\",\n            dependencies: [\"MyLibrary\"]\n        ),\n    ]\n)\n```\n\n## Running Tests\n\n```bash\nswift test                          # run all tests\nswift test --parallel               # parallel execution\nswift test --filter \"AddTests\"      # run specific test class\nswift test --filter \"testAdd\"       # run tests matching pattern\nswift test --enable-code-coverage   # with coverage\n\nxcodebuild test \\\n    -scheme MyApp \\\n    -destination 'platform=iOS Simulator,name=iPhone 16'\n```\n\n## Coverage\n\n```bash\nswift test --enable-code-coverage\nllvm-cov report \\\n    .build\u002Fdebug\u002FMyLibraryPackageTests.xctest\u002FContents\u002FMacOS\u002FMyLibraryPackageTests \\\n    --instr-profile=.build\u002Fdebug\u002Fcodecov\u002Fdefault.profdata\n```\n\n```bash\n# Using xccov (Xcode)\nxcodebuild -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 16' \\\n    -enableCodeCoverage YES test\nxcrun xccov view --report --json DerivedData\u002F**\u002FLogs\u002FTest\u002F*.xcresult\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: macos-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - run: swift test --enable-code-coverage\n      - run: xcrun llvm-cov export -format=lcov .build\u002Fdebug\u002F*.xctest -instr-profile .build\u002Fdebug\u002Fcodecov\u002Fdefault.profdata > coverage.lcov\n```\n\n## Flaky Tests Guardrails\n\n- Never use `sleep()` for synchronization; use `XCTestExpectation`.\n- Make test data unique per test with UUID-based identifiers.\n- Mock network calls using protocol-based dependency injection.\n- Use `continueAfterFailure = false` carefully — prefer testing one failure at a time.\n- Reset app state between UI tests by launching fresh.\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, nil, and just-outside valid ranges.\n\n```swift\n\u002F\u002F Tests\u002FValidatorTests.swift\nfinal class ValidatorTests: XCTestCase {\n    func testRejectsInvalidInput() {\n        XCTAssertThrowsError(try validator.validate(\"\")) { error in\n            XCTAssertTrue(error is ValidationError)\n        }\n        let longInput = String(repeating: \"a\", count: 10001)\n        XCTAssertThrowsError(try validator.validate(longInput))\n    }\n}\n```\n\n### 2. Negative \u002F Error Case Testing\nVerify the system behaves correctly under invalid or unexpected conditions.\n\n```swift\n\u002F\u002F Tests\u002FCalculatorTests.swift\nfinal class CalculatorTests: XCTestCase {\n    func testThrowsOnDivideByZero() {\n        XCTAssertThrowsError(try 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```swift\n\u002F\u002F Tests\u002FConnectionTests.swift\nfinal class ConnectionTests: XCTestCase {\n    func testStateTransitions() {\n        let conn = Connection()\n        XCTAssertEqual(conn.state, .closed)\n        conn.open()\n        XCTAssertEqual(conn.state, .open)\n        conn.close()\n        XCTAssertEqual(conn.state, .closed)\n        \u002F\u002F Idempotency\n        conn.close()\n        XCTAssertEqual(conn.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 `XCTAssertEqual(actual, expected, \"descriptive message\")` or Swift Testing `#expect(actual == expected)`.*\n- **Happy Path Bias**: Only testing successful scenarios, leaving error paths uncovered. *Fix: Test `nil` values with `XCTAssertNil`\u002F`XCTAssertNotNil`, `XCTAssertThrowsError` for exceptions.*\n- **Mock Overdose**: Too many protocol mocks hiding integration issues. *Fix: Mock only at service boundaries; prefer real implementations for value types.*\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 `XCTestCase` methods with no clear setup\u002Fverify structure. *Fix: Follow AAA, use `setUpWithError()`\u002F`tearDownWithError()`, keep test methods focused.*\n- **Flaky Test**: Non-deterministic results from async, UI, or test order. *Fix: Use `XCTestExpectation` with timeouts, `continueAfterFailure = false`, test isolation.*\n\n## Best Practices\n\n### DO\n\n- Use descriptive `testXxx` method names (e.g., `testAdd_WithPositiveNumbers_ReturnsSum`)\n- Use `XCTestExpectation` + `wait(for:timeout:)` for async code\n- Use `throws` functions to avoid `try?` in tests\n- Use `#fileID` \u002F `#line` for helper assertion functions\n- Separate unit, integration, and UI tests into separate targets\n\n### DON'T\n\n- Don't use `sleep()` for synchronization\n- Don't depend on real network or time in unit tests\n- Don't share mutable state between test methods\n- Don't test private methods directly — test through public API\n- Don't write UI tests that depend on specific screen sizes without layout checks\n\n### Common Pitfalls\n\n- **Flaky async tests** → Always use `XCTestExpectation` with timeout.\n- **Shared state** → Reset in `setUp()` \u002F `tearDown()`.\n- **Hardcoded delays** → Use `waitForExistence(timeout:)` in UI tests.\n- **Network in unit tests** → Mock `URLProtocol` or use protocol-based DI.\n- **Slow UI tests** → Mark slow tests with `-[XCUIApplication launch]` per test.\n- **Missing coverage gates** → Add `--enable-code-coverage` in CI.\n\n## Optional: Swift Testing Framework (Swift 6+)\n\nThe new Swift Testing framework (available in Swift 6+) is the modern alternative:\n\n```swift\nimport Testing\n\n@Test(\"Adds two numbers\")\nfunc addTest() {\n    #expect(add(2, 3) == 5)\n}\n\n@Test(\"Parametrized addition\",\n    arguments: [(1, 2, 3), (-1, 1, 0), (0, 0, 0)])\nfunc addParametrized(a: Int, b: Int, expected: Int) {\n    #expect(add(a, b) == expected)\n}\n```\n\n## Alternatives\n\n- **Quick + Nimble** (v7.x): BDD-style testing with expressive matchers.\n- **Swift Testing**: Apple's new test framework (Swift 6+), modern macro-based API.\n",{"name":5,"metadata":24,"description":27,"compatibility":28},{"author":25,"source":26},"github-spec-kit","templates\u002Fpassive-skills\u002Fswift-testing\u002FSKILL.md","Use ONLY when user explicitly requests Swift test code, XCTest\u002FSwift Testing configuration, test failure diagnosis, or coverage improvement for Swift\u002FApple-platform projects.\nTriggers: \"write test swift\", \"XCTest\", \"swift testing\", \"@Test macro\", \"xcode test\", \"swift coverage\", \"XCUITest\", \"Quick Nimble\".\nDo NOT activate for: general Swift coding without test context, SPM\u002FPackage.swift setup, Xcode project configuration, or SwiftUI\u002FUIKit implementation without test needs. ","Requires spec-kit project structure with .specify\u002F directory","main","021f5cbe02157229460a577e9a585f2da6d78cb0",".codex\u002Fskills\u002Fswift-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 swift-testing",{"tool":41,"command":42},"bunx","bunx skills add chenziyang110\u002Flaunchdeck --skill swift-testing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add chenziyang110\u002Flaunchdeck --skill swift-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fswift-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",[],[]]