Menu
Build an individual Swift package for testing
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build the project for testing
Build the project
Take the current plan all the way to a ready-to-merge pull request — review the plan (scaled to risk), implement it test-first, code-review and fix, security-review, verify the acceptance criteria, open the PR, and watch it green. Use after you have an approved plan (e.g. from plan mode) and want the rest of the feature pipeline run end-to-end. Invoking it is itself plan approval — it then runs autonomously to a single hard stop: ready-to-merge.
Run a specific test target or test class
Run all unit tests
Run snapshot tests
| name | build-package-for-testing |
| description | Build an individual Swift package for testing |
Build a single Swift package including its test targets — use this to verify one
package's tests compile; use /build-for-testing for the entire app.
The xcode MCP builds the whole Xcode project, not a single SwiftPM package, so it does not apply here — this skill uses the
swiftCLI directly.
Delegate to a Haiku subagent (subagent_type: general-purpose, model: haiku)
so the output stays out of your context. Do not run it yourself. Give it the
prompt below, then relay its report.
Subagent prompt:
Build the Swift package (including test targets) at <package-dir> and report concisely:
cd <package-dir> && swift build --build-tests -Xswiftc -warnings-as-errors 2>&1
MANDATORY cleanup afterwards: `rm -rf <package-dir>/.build`. Leaving a package
`.build` directory behind causes later `make test` simulator-install failures.
Report back ONLY:
- Status: succeeded or failed
- Each error/warning as `file:line — message` (omit if none; warnings are errors)
Do not paste raw logs or successful-compilation output.
Note: packages whose test targets import UIKit (e.g. snapshot-test targets) can't build their test targets via
swift build --build-testson macOS. For those, build sources only (/build-package) or use the full-app/build-for-testing.
| Layer | Path pattern |
|---|---|
| Contexts | Contexts/<PackageName>/ |
| Context Adapters | Adapters/Contexts/<PackageName>/ |
| Platform Adapters | Adapters/Platform/<PackageName>/ |
| Features | Features/<PackageName>/ |
| Core | Core/<PackageName>/ |
| Platform | Platform/<PackageName>/ |
| AppDependencies | AppDependencies/ |