Menü
Run a specific test target or test class
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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 all unit tests
Run snapshot tests
Capture durable, project-specific learnings from the work just done into the knowledge/ base — gotchas, implementation quirks, tooling traps, SwiftData/CloudKit & TMDb-mapping surprises, things looked up or web-searched, and design decisions (as ADRs). Use before opening a PR (it runs automatically in /deliver), or any time you've learned something worth remembering. Records only non-obvious, reusable facts; skips anything already in the repo, CLAUDE.md, or git history.
| name | test-single |
| description | Run a specific test target or test class |
| arguments | $ARGUMENTS |
Run a subset of the app's test suite by specifying a test target, class, or method
($ARGUMENTS). <specifier> is the -only-testing value: a test target,
Target/ClassName, or Target/ClassName/methodName.
Preferred — Xcode MCP (xcode), when running inside Xcode. Call it directly:
tabIdentifier from mcp__xcode__XcodeListWindows.mcp__xcode__GetTestList (with the
tabIdentifier) to find targets/classes.mcp__xcode__RunSomeTests with the tabIdentifier and the specifier(s)
matching $ARGUMENTS. On a build failure, call mcp__xcode__GetBuildLog with the
tabIdentifier and severity: "error".Fallback — make, when the MCP isn't available. For a long-running run you'll block on (e.g. a /deliver pre-PR gate step), prefer a backgrounded Bash (run_in_background: true) that redirects to a log and appends ; echo "EXIT=$?", then — on the completion notification — grep the log for the EXIT= marker plus failing tests (targeted greps keep the verbose log out of context); it self-reports once on exit, whereas a Haiku subagent driving its own poll loop tends to return premature "still waiting" notes. Otherwise, delegate to a Haiku subagent
(subagent_type: general-purpose, model: haiku) so output stays out of your context.
Do not run it yourself. Prompt the subagent to:
Run `mkdir -p .build && make test TEST_TARGET=<specifier> > .build/last-test.log 2>&1`,
check the exit status, and report ONLY:
- Status: passed or failed
- Counts: total / passed / failed
- Each failing test as `SuiteName/testName` with its `file:line` and message (omit if none)
- On failure, the log path `.build/last-test.log`
Do not paste passing-test output or raw logs.
MovieDetailsFeatureTests # whole target
MovieDetailsFeatureTests/MovieDetailsViewModelTests # a class/suite
MovieDetailsFeatureTests/MovieDetailsViewModelTests/loadSuccess # one test