mcpField
T
test-triage

test-triage

github.com/openaiTesting & quality7.7k53 installsUpdated 3w ago
Repository

About test-triage

test-triage is a testing skill for Xcode and SwiftPM projects. It narrows test runs, classifies failures, and recommends a focused next step.

Key features

  1. 01Detects Xcode or SwiftPM test harnesses
  2. 02Starts with the smallest relevant test scope
  3. 03Classifies build, assertion, crash, timing, and setup failures
  4. 04Uses focused reruns and summarizes next steps

Use cases

  1. 01Triage a failure in an Xcode test target
  2. 02Investigate a failing SwiftPM test
  3. 03Distinguish a flaky test from a product defect

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/openai/plugins --skill test-triage

After installing, type/test-triagein Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

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 test for Xcode-based projects.
    • Use swift test for 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

Comments

Markdown supported