skills.rest
HKU-MMLab
HKU-MMLabOFFICIAL
Explore all skills by this author →
GitHub

test-runner

Parses test results from CI logs and reports to categorize failures and summarize suite status.

39|1|Updated Jul 2, 2026
Search Tags:#pytest#flaky tests#coverage#test results#pr triage#ci status#junit xml
One-click install
npx skills add https://github.com/HKU-MMLab/UniClawBench --skill test-runner-hku-mmlab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-runner
Source: https://github.com/HKU-MMLab/UniClawBench/tree/main/injection/101_skill_usage/task_101_27_pr_triage/skills/test-runner
Command: npx skills add https://github.com/HKU-MMLab/UniClawBench --skill test-runner-hku-mmlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reading CI logs and test reports to determine whether a pull request is safe to merge is slow and error-prone, especially when flaky tests and infrastructure failures are mixed with genuine bugs. ## Core Features & Use Cases - Test Result Parsing: Reads pytest JSON, JUnit XML, CI log fragments, and test result JSON to extract pass/fail counts. - Failure Categorization: Distinguishes genuine bugs from flaky tests and infrastructure issues, and detects flaky tests across multiple runs. - PR Readiness Checks: Evaluates PR metadata with CI status fields and returns a verdict of green, red, or flaky, plus coverage summaries from coverage reports. - Use Case: During PR triage, ask for the CI status of a pull request and receive a structured summary with total tests, failures by category, and a merge-readiness verdict. ## Quick Start Check the test status for this PR and summarize which tests are failing and why.

Frequently Asked Questions about test-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check CI test status for a pull request?▼

Provide the PR metadata or CI log output and ask for the test status. The skill parses the results and returns total tests, passed, failed, skipped, and flaky counts along with a green, red, or flaky verdict.

How to identify flaky tests in recent test runs?▼

Supply test results from multiple runs, such as the last 10 CI executions, and ask to find flaky tests. The skill compares outcomes across runs and flags tests that alternate between passing and failing.

What test frameworks and report formats are supported?▼

The skill supports pytest, jest, mocha, and go test output, plus generic JUnit XML reports. It can also read CI log fragments and test result JSON when direct test execution is not possible.

Can test results be analyzed without running the test suite?▼

Yes. In snapshot-only environments where execution is impossible, the skill reads existing CI metadata or stored test result JSON files and produces the same structured summary and verdict.

Why does a test suite show failures that are not real bugs?▼

Failures often come from flaky tests or infrastructure issues rather than genuine code defects. The skill categorizes each failure by type so you can distinguish real bugs from environmental noise before merging.

Related Skills

Explore More Software Engineering Skills→
orekyuuorekyuu

junit-report-collector

Collect JUnit XML test reports and summarize pass, fail, and skip results.

Community
Intermediate
HeyvhuangHeyvhuang
339

review-quality

Automate merge-ready quality review of code changes with structured reports.

Community
Advanced
rm2thaddeusrm2thaddeus
4

code-auditor

Analyze codebases for architecture, quality, security, performance, and maintainability.

Community
Advanced
Jin9Jin9

executing-backend-unit-tests

Execute backend unit tests in a sandbox and emit a coverage-gated PASS, FAIL, or ERROR verdict.

Community
Advanced