Swift Testing Code Review
CheckedHelps with Swift, testing, code review as part of building frontend UIs and user experiences workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add existential-birds/beagle --skill swift-testing-code-review -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
existential-birds
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned existential-birds/beagle at d1a74899fb.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- d1a74899fb
- Scanned
- 5 files, 583 lines
About this skill
What it does
This skill assists with reviewing Swift code, specifically focusing on testing practices for frontend UI and user experience development. It provides guidance and references related to common testing patterns like #expect vs #require, parameterized tests, async sequences, and test organization using @Suite. The tool helps ensure adherence to best practices in Swift testing, improving code quality and reliability.
When to use it
- When reviewing code that utilizes the
#expector#requiremacros for assertions. - During reviews of tests employing arguments or traits within
@Testfunctions. - When assessing asynchronous testing approaches involving confirmation and completion handlers.
- For evaluating the organization of test suites using
@Suiteand related features.
Key capabilities
- Provides references to documentation on
#expectvs#require, expression capture, and error testing (references/expect-macro.md). - Offers guidance on parameterized tests with arguments and traits (
references/parameterized.md). - Covers best practices for asynchronous sequences and completion handlers (
references/async-testing.md). - Details test organization using
@Suite, tags, parallel execution, and serialization (references/organization.md). - Includes a checklist of common review points related to Swift testing conventions.
Example prompts
- "Review this code snippet for proper use of
#expectand#require." - "Check if these parameterized tests are using
zip()correctly." - "Assess the organization of this test suite, paying attention to
.serializedusage."
Tips & gotchas
- The skill focuses specifically on Swift testing practices; it is not a general code review tool.
- Pay close attention to the checklist provided for common pitfalls in Swift testing.
- Reviewing completion handlers should use
withCheckedContinuation, notconfirmation.