← Back to Skills Marketplace
Swift Testing Code Review
by
Kevin Anderson
· GitHub ↗
· v1.2.1
· MIT-0
168
Downloads
0
Stars
1
Active Installs
2
Versions
Install in OpenClaw
/install swift-testing-code-review
Description
Reviews Swift Testing code for proper use of
README (SKILL.md)
Swift Testing Code Review
Hard gates
Complete in order before recording Swift Testing review findings. Stack with beagle-ios:review-verification-protocol for universal review rules.
- Scope: You have an explicit list of
.swiftpaths under review (or a user-named single file). Pass: Paths captured in working notes or one line:No Swift files in scope— then stop with no findings. - Swift Testing surface: For each path you treat as Swift Testing code, confirm
import Testingor@Test/#expect/#require/@Suiteappears in that file (open or search). Pass: At least one match per critiqued file, or you exclude that file from Swift Testing review with a one-line reason (e.g. XCTest-only). - Evidence + protocol: Load
beagle-ios:review-verification-protocolbefore asserting any issue. Pass: Each finding meets that skill’s anchor rules; any violated Review Checklist item cites[FILE:LINE]evidence. If you report zero issues, stateProtocol applied; no Swift Testing issues(or equivalent) in the review summary.
Quick Reference
| Issue Type | Reference |
|---|---|
| #expect vs #require, expression capture, error testing | references/expect-macro.md |
| @Test with arguments, traits, zip() pitfalls | references/parameterized.md |
| confirmation, async sequences, completion handlers | references/async-testing.md |
| @Suite, tags, parallel execution, .serialized | references/organization.md |
Review Checklist
- Expressions embedded directly in
#expect(not pre-computed booleans) -
#requireused only for preconditions,#expectfor assertions - Error tests check specific types (not generic
(any Error).self) - Parameterized tests with pairs use
zip()(not Cartesian product) - No logic mirroring implementation in parameterized expected values
- Async sequences tested with
confirmation(expectedCount:) - Completion handlers use
withCheckedContinuation, notconfirmation -
.serializedapplied only where necessary (shared resources) - Sibling serialized suites nested under parent if mutually exclusive
- No assumption of state persistence between
@Testfunctions - Disabled tests have explanations and bug links
When to Load References
- Reviewing #expect or #require usage -> expect-macro.md
- Reviewing @Test with arguments or traits -> parameterized.md
- Reviewing confirmation or async testing -> async-testing.md
- Reviewing @Suite or test organization -> organization.md
Review Questions
- Could pre-computed booleans in
#expectlose diagnostic context? - Is
#requirestopping tests prematurely instead of revealing all failures? - Are multi-argument parameterized tests creating accidental Cartesian products?
- Could
zip()silently drop test cases due to unequal array lengths? - Are completion handlers incorrectly tested with
confirmation?
Usage Guidance
This skill is instruction-only and appears coherent for reviewing Swift Testing code. Before installing/using it: ensure you trust the agent's file access (it will open .swift files in scope), verify the external protocol it references (beagle-ios:review-verification-protocol) is a trusted skill or resource, and note that the metadata lacks a source/homepage — if provenance matters, ask the publisher for more info. It does not request credentials or install anything.
Capability Analysis
Type: OpenClaw Skill
Name: swift-testing-code-review
Version: 1.2.1
The skill bundle is a legitimate tool designed to guide an AI agent in reviewing Swift Testing code. It contains comprehensive reference documentation (references/async-testing.md, references/expect-macro.md, etc.) and structured instructions in SKILL.md that enforce best practices for the Swift Testing framework. There are no signs of data exfiltration, malicious execution, or harmful prompt injection; the 'hard gates' and checklists are focused entirely on improving code review quality and diagnostic accuracy.
Capability Assessment
Purpose & Capability
The skill's name, manifest, and SKILL.md all describe reviewing Swift Testing constructs (#expect/#require, parameterized tests, async testing, organization). It requests no unrelated binaries, env vars, or config paths, so its declared needs are proportionate to a code-review task. (Minor note: the top-line description in metadata is truncated and the skill's source/homepage are unknown.)
Instruction Scope
Runtime instructions are narrowly scoped to inspecting .swift files that contain Swift Testing markers and to citing FILE:LINE evidence; they explicitly require loading a separate review protocol (beagle-ios:review-verification-protocol) before reporting issues. There are no directives to read unrelated system files, export secrets, or call external endpoints. The external protocol dependency is a functional dependency (not a direct security red flag) but you should verify that the referenced protocol skill is trusted.
Install Mechanism
No install spec and no code files — instruction-only — so nothing is written to disk or fetched during install.
Credentials
The skill requests no environment variables, credentials, or config paths. All checks operate on repository files and included reference docs which is proportionate for a code review.
Persistence & Privilege
always is false and the skill does not request persistent system presence or modify other skills' configurations. Autonomous invocation is enabled by default but not combined with other concerning factors.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install swift-testing-code-review - After installation, invoke the skill by name or use
/swift-testing-code-review - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.1
Swift Testing review protocol integration.
- Added "Hard gates" section requiring explicit scoping of reviewed Swift files and confirmation of Swift Testing surface before review.
- Mandated loading of `beagle-ios:review-verification-protocol` and evidence citing for each finding.
- Specified standardized phrasing for zero-issue reviews.
- No changes to core checklist or references.
v1.2.0
Version 1.2.0 introduces a clear reference and checklist system for Swift Testing code reviews.
- Added quick reference table mapping common test code issues to specific guidance documents.
- Provided a detailed checklist for consistent code review, covering expectations, async patterns, and test organization.
- Included contextual advice on when to consult each reference during reviews.
- Added review questions to spotlight common pitfalls and best practices.
Metadata
Frequently Asked Questions
What is Swift Testing Code Review?
Reviews Swift Testing code for proper use of. It is an AI Agent Skill for Claude Code / OpenClaw, with 168 downloads so far.
How do I install Swift Testing Code Review?
Run "/install swift-testing-code-review" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Swift Testing Code Review free?
Yes, Swift Testing Code Review is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Swift Testing Code Review support?
Swift Testing Code Review is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Swift Testing Code Review?
It is built and maintained by Kevin Anderson (@anderskev); the current version is v1.2.1.
More Skills