Test Triage
- 21 installs
- 4.9k repo stars
- Updated July 14, 2026
- openai/plugins
test-triage classifies macOS test failures from scoped Xcode or SwiftPM runs.
About
The test-triage skill narrows macOS test failures without treating every red test as a product bug. It detects whether xcodebuild test or swift test is appropriate, runs the smallest meaningful scope using targets or filters when provided, and classifies outcomes as build failure, assertion failure, crash, async flake, environment setup, or entitlement issues. Focused reruns avoid full-suite loops without new signal. Output reports the command, smallest failing scope, top failure category, likely cause, and next proof step. Guardrails separate compilation from execution failures, flag iOS-only assumptions on macOS, and mark probable flakes without overstating confidence. Detects Xcode versus SwiftPM harness automatically. Runs smallest failing target or filter first. Classifies build, assertion, crash, flake, and setup failures. Recommends focused reruns over full-suite loops. Summarizes command, scope, category, and next step. Clear failure category with command, scope, and next rerun step.
- Detects Xcode versus SwiftPM harness automatically.
- Runs smallest failing target or filter first.
- Classifies build, assertion, crash, flake, and setup failures.
- Recommends focused reruns over full-suite loops.
- Summarizes command, scope, category, and next step.
Test Triage by the numbers
- 21 all-time installs (skills.sh)
- +1 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #1,425 of 2,154 Testing & QA skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
test-triage capabilities & compatibility
- Capabilities
- harness detection workflow · failure classification taxonomy · focused rerun guardrails
- Use cases
- testing · debugging
- Platforms
- macOS
- IDEs
- vscode
What test-triage says it does
run the smallest meaningful test scope first
Distinguish compilation failures from test execution failures
npx skills add https://github.com/openai/plugins --skill test-triageAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 21 |
|---|---|
| repo stars | ★ 4.9k |
| Last updated | July 14, 2026 |
| Repository | openai/plugins ↗ |
How do I triage failing macOS tests?
Triage macOS test failures across Xcode and SwiftPM with scoped runs and precise failure classification.
Who is it for?
macOS developers debugging Xcode or SwiftPM test suites.
Skip if: Skip for Linux-only packages without Apple test harnesses.
When should I use this skill?
User narrows test failures, explains assertions, or separates setup from regressions.
What you get
Clear failure category with command, scope, and next rerun step.
Files
Test Triage
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.
Workflow
1. Detect the test harness.
- Use
xcodebuild testfor Xcode-based projects. - Use
swift testfor SwiftPM packages.
2. 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.
3. 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
4. Rerun intelligently.
- Use focused reruns when a specific case fails.
- Avoid burning time on full-suite reruns without new information.
5. 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
interface:
display_name: "Test Triage"
short_description: "Run and explain macOS test failures with focused reruns"
default_prompt: "Use $test-triage to run the smallest meaningful macOS test scope first, classify failures correctly, and summarize the next best rerun or fix."
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3kFAQ
What does test-triage do?
test-triage classifies macOS test failures from scoped Xcode or SwiftPM runs.
When should I use test-triage?
User narrows test failures, explains assertions, or separates setup from regressions.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.