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.

483 stars 20 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add twostraws/Swift-Testing-Agent-Skill

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add twostraws/Swift-Testing-Agent-Skill --skill swift-testing-pro
Manual install
git clone --depth 1 https://github.com/twostraws/Swift-Testing-Agent-Skill.git /tmp/Swift-Testing-Agent-Skill
mkdir -p ~/.claude/skills
cp -r /tmp/Swift-Testing-Agent-Skill/swift-testing-pro ~/.claude/skills/swift-testing-pro

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

Write and review Swift Testing code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems - do not nitpick or invent issues.

Review process:

1. Ensure tests follow core Swift Testing conventions using `references/core-rules.md`.
1. Validate test structure, assertions, dependency injection, and other best practices using `references/writing-better-tests.md`.
1. Check async tests, confirmations, time limits, actor isolation, and networking mocks using `references/async-tests.md`.
1. Ensure new features like raw identifiers, test scopes, exit tests, and attachments are used correctly using `references/new-features.md`.
1. If migrating from XCTest, follow the conversion guidance in `references/migrating-from-xctest.md`.

If doing partial work, load only the relevant reference files.

## 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.
Read the full skill on GitHub

Details

Skill name
swift-testing-pro
Path
swift-testing-pro/SKILL.md
License
MIT
Repo updated
17 May 2026
Copies
Found in 2 GitHub repos

FAQ

What does the Swift Testing Pro skill do?

Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.

How do I install the Swift Testing Pro skill?

Claude Code plugin: /plugin marketplace add twostraws/Swift-Testing-Agent-Skill. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Swift Testing Pro popular?

It lives in twostraws/Swift-Testing-Agent-Skill, which has 483 GitHub stars and 20 forks.

Related skills

Ab Test Setup

1.2k

borghei/Claude-Skills

Design and analyze A/B tests: sample size, test duration, and statistical significance for conversion experiments. Use when setting up an A/B test, calculating sample size, designing an experiment, or analyzing results.

Testing & QAIn 1 list217

Tool Design Sprint Test and Score

819

product-on-purpose/pm-skills

Day 5 (Friday) sprint-closing move of a Design Sprint that produces the bundled Friday artifact covering per-customer interview observations, best quotes, scorecard grid (sprint questions by customers), observed patterns, hot takes from each team member, and the Decider summary (build, iterate, pivot, or stop, plus highest-confidence learning, most important revision, and next artifact). Use Friday after Thursday's prototype passes trial run and during/after the 5 customer interviews. The sprint's payoff artifact.

Testing & QAIn 2 lists104

Ab Test Setup

1.2k

borghei/Claude-Skills

Design and run statistically rigorous A/B tests and experiments. Use when planning experiments, calculating sample sizes, designing test variants, selecting metrics, analyzing results, or when someone says "let's test that.

Testing & QAIn 1 list217

Measure Experiment Results

819

product-on-purpose/pm-skills

Documents the results of a completed experiment or A/B test with statistical analysis, learnings, and recommendations. Use after experiments conclude to communicate findings, inform decisions, and build organizational knowledge.

Testing & QAIn 2 lists104

API Test Suite Builder

1.2k

borghei/Claude-Skills

Generates API test skeletons from an OpenAPI spec, measures which endpoints tests really assert on, and checks response samples against the spec. Use when adding API tests, auditing API test coverage, or catching contract drift.

Testing & QAIn 1 list217

Measure Experiment Design

819

product-on-purpose/pm-skills

Designs an A/B test or experiment with variants, success metrics, sample size, and duration for an existing hypothesis. Use when planning an experiment to validate a product change or test an assumption you have already framed. To articulate the hypothesis itself first, use define-hypothesis.

Testing & QAIn 2 lists104

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.