
test-triage
✓ Official★ 4,000by openai · part of openai/plugins
Triage failing macOS tests across Xcode and SwiftPM workflows. Use when asked to run macOS tests, narrow failing scopes, explain assertion or crash failures,…
This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.
name: test-triage description: Triage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.
Test Triage
Workflow
-
Detect the test harness.
- Use
xcodebuild testfor Xcode-based projects. - Use
swift testfor SwiftPM packages.
- Use
-
Narrow the scope.
- If the user gave a target, product, or test filter, use it.
- If not, prefer the smallest likely failing target before a full suite.
-
Classify the result.
- Build failure
- Assertion failure
- Crash or signal
- Async timing or flake
- Environment or fixture setup issue
- Missing entitlement or host app issue
-
Rerun intelligently.
- Use focused reruns when a specific case fails.
- Avoid burning time on full-suite reruns without new information.
-
Summarize clearly.
- What command ran
- Which tests failed
- What kind of failure it was
- The best next proof step or fix path
Guardrails
- Distinguish compilation failures from test execution failures.
- Call out when a test appears to assume iOS-only or simulator-only behavior.
- Mark likely flakes as such instead of overstating confidence.
Output Expectations
Provide:
- the command used
- the smallest failing scope
- the top failure category
- a concise explanation of the likely cause
- the next rerun or fix step
npx skills add https://github.com/openai/plugins --skill test-triageRun this in your project — your agent picks the skill up automatically.
Quick Start
Use this skill to run the smallest meaningful test scope first, classify failures precisely, and avoid treating every test failure like a product bug.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.