Agent Skills
› robinebers/openusage
› test-triage
test-triage
GitHub用于在 macOS 环境下通过 Xcode 或 SwiftPM 运行测试,精准定位失败范围,分类构建、断言、崩溃等故障类型,区分真实回归与环境问题,并提供清晰的复现命令与修复建议。
Trigger Scenarios
运行 macOS 测试
缩小失败测试范围
解释断言或崩溃原因
区分真实回归与环境问题
Install
npx skills add robinebers/openusage --skill test-triage -g -y
SKILL.md
Frontmatter
{
"name": "test-triage",
"description": "Triage failing macOS tests across Xcode and SwiftPM workflows. Use when asked to run macOS tests, narrow failing scopes, explain assertion or crash failures, or separate real test regressions from setup and environment problems."
}
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
-
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
Version History
- 70acd4f Current 2026-08-20 09:02


