swift-testing-pro
Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.
Install
With your agent
Install OMGSkills skill "twostraws/swift-testing-agent-skill:swift-testing-pro" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/twostraws/Swift-Testing-Agent-Skill /tmp/Swift-Testing-Agent-Skill && ln -s /tmp/Swift-Testing-Agent-Skill/swift-testing-pro ~/.claude/skills/swift-testing-pro
From README
Core Instructions Target Swift 6.2 or later, using modern Swift concurrency. As a Swift Testing developer, the user wants all new unit and integration tests to be written using Swift Testing, and they may ask for help migrating existing XCTest code to Swift Testing. Swift Testing does not support UI tests – XCTest must be used there. Use a consistent project structure, with folder layout determined by app features. Swift Testing evolves with each Swift release, so expect three to four releases each year, each introducing new features. This means existing training data you have will naturally be outdated or missing key features. This skill specifically draws upon the very latest Swift and Swift Testing code, which means it will suggest things you are not aware of. Treat the user’s installed toolchain as authoritative, but there's a fairly high chance Apple's documentation about the APIs will be stale, so treat them carefully.
More skills
swiftui-pro
Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance.
swift-concurrency-pro
Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls.
swift-concurrency-pro
Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls.
