Swig Test
swig/swig
Run SWIG test suite for specific languages. An agent skill from swig/swig.
Fetch a Prow job run summary from Sippy showing all failed tests grouped by SIG with error messages
Install Fetch Job Run Summary
$ npx skills add openshift-eng/ai-helpers --skill fetch-job-run-summary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-job-run-summary --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ci/skills/fetch-job-run-summary .claude/skills/fetch-job-run-summary && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "fetch-job-run-summary" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-job-run-summary into .claude/skills/fetch-job-run-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-job-run-summary", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-job-run-summaryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openshift-eng/ai-helpers --skill fetch-job-run-summary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-job-run-summary --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ci/skills/fetch-job-run-summary .agents/skills/fetch-job-run-summary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fetch-job-run-summary" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-job-run-summary into .agents/skills/fetch-job-run-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-job-run-summary", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-eng/ai-helpers --skill fetch-job-run-summary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-job-run-summary --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ci/skills/fetch-job-run-summary .cursor/skills/fetch-job-run-summary && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "fetch-job-run-summary" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-job-run-summary into .cursor/skills/fetch-job-run-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-job-run-summary", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openshift-eng/ai-helpers.git --path plugins/ci/skills/fetch-job-run-summary--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openshift-eng/ai-helpers --skill fetch-job-run-summary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-job-run-summary --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ci/skills/fetch-job-run-summary .gemini/skills/fetch-job-run-summary && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "fetch-job-run-summary" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-job-run-summary into .gemini/skills/fetch-job-run-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-job-run-summary", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openshift-eng/ai-helpers fetch-job-run-summaryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openshift-eng/ai-helpers --skill fetch-job-run-summary -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ci/skills/fetch-job-run-summary .github/skills/fetch-job-run-summary && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "fetch-job-run-summary" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-job-run-summary into .github/skills/fetch-job-run-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-job-run-summary", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-eng/ai-helpers --skill fetch-job-run-summary -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-job-run-summary --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ci/skills/fetch-job-run-summary .opencode/skills/fetch-job-run-summary && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "fetch-job-run-summary" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-job-run-summary into .opencode/skills/fetch-job-run-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-job-run-summary", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
fetch-job-run-summary- GitHub stars
- 120
- Token cost
- ~1.3k tokens
- SKILL.md length
- 502 words
- Files
- 2
- Skills in repo
- 118
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Fetch a Prow job run summary from Sippy showing all failed tests grouped by SIG with error messages
- Works in 2 steps: Python 3: Version 3.6 or later → Network Access: Must be able to reach…
- Tasks that involve Failing and flaky tests
- SKILL.md covers When to Use This Skill, Prerequisites, Implementation and API Details, plus 4 more sections
- Runs Python scripts from its folder; calls python3; reaches sippy.dptools.openshift.org and prow.ci.openshift.org
What it does
Fetch Job Run Summary is an agent skill from openshift-eng/ai-helpers. Fetch a Prow job run summary from Sippy showing all failed tests grouped by SIG with error messages
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `fetch_job_run_summary.py`).
It sits in Testing & QA, covering Failing and flaky tests. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Failing and flaky tests
Example prompts
- “/fetch-job-run-summary”
Requirements
- Python 3
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Python 3: Version 3.6 or later
- Network Access: Must be able to reach https://sippy.dptools.openshift.org
What it can do on your machine
Read from SKILL.md and the folder at commit a627176. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
sippy.dptools.openshift.orgprow.ci.openshift.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Fetch Job Run Summary loads about 1.3k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 502 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 502 words, ~1,299 tokens.
Download SKILL.mdSave it as
.claude/skills/fetch-job-run-summary/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- fetch-job-run-summary
- description
- Fetch a Prow job run summary from Sippy showing all failed tests grouped by SIG with error messages
Fetch Job Run Summary
This skill fetches a summary of a Prow job run from the Sippy API, listing all tests that failed (excluding flakes) along with their error messages.
When to Use This Skill
Use this skill when you need to:
- List all tests that failed in a specific Prow job run
- Understand which components are affected by failures in a job
- Identify dominant error patterns across multiple test failures
- Investigate mass test failure regressions by examining the underlying test failures
- Get a quick overview of a job run's health (pass rate, infrastructure failure, etc.)
Prerequisites
- Python 3: Version 3.6 or later
- Network Access: Must be able to reach
https://sippy.dptools.openshift.org
Implementation
script_path="plugins/ci/skills/fetch-job-run-summary/fetch_job_run_summary.py"
# Text output (AI-readable)
python3 "$script_path" <prow_job_run_id>
# JSON output (structured)
python3 "$script_path" <prow_job_run_id> --format jsonParameters
| Parameter | Required | Description |
|---|---|---|
prow_job_run_id | Yes | The Prow job run ID (numeric, e.g., 2030845545290928128) |
--format | No | Output format: text (default) or json |
Extracting a Job Run ID
The job run ID can be extracted from a Prow job URL:
https://prow.ci.openshift.org/view/gs/test-platform-results-public/logs/<job-name>/<job_run_id>The last path segment is the job run ID.
API Details
Endpoint: https://sippy.dptools.openshift.org/api/job/run/summary
Query Parameter: prow_job_run_id (required)
Response Fields:
| Field | Type | Description |
|---|---|---|
id | int | Prow job run ID |
name | string | Full job name |
release | string | OpenShift release (e.g., 4.22) |
cluster | string | Build cluster (e.g., build01) |
url | string | Prow job URL |
startTime | string | ISO 8601 start time |
durationSeconds | int | Job duration in seconds |
overallResult | string | S (success) or F (failure) |
reason | string | Human-readable result reason |
infrastructureFailure | bool | Whether this was an infrastructure failure |
testCount | int | Total number of tests run |
testFailureCount | int | Number of failed tests |
testFailures | dict | Map of test name to error message (excludes flakes) |
variants | list | Job variant tags |
Flake Handling
The Sippy API automatically handles flake detection. When a test has both a failure and a pass in the same job run's junit results (the standard flake pattern), it is not included in testFailures. Only true failures — tests that failed without a corresponding pass — appear in the results.
Show full SKILL.md (188 more words)Show less
Output
Text Format
The text output is structured for AI consumption with:
- Job Run Summary: Metadata (job name, release, duration, result, variants)
- Test Statistics: Total tests, failures, pass rate
- Failed Tests: Failure count (sorted by count descending)
- Dominant Error Patterns: Error messages appearing in >5% of failures, with counts
- Detailed Failures: Each failed test with its error message, grouped by SIG
JSON Format
Structured JSON with the same data:
{
"success": true,
"job_name": "periodic-ci-openshift-hypershift-...",
"job_run_id": "2030845545290928128",
"release": "4.22",
"test_count": 3827,
"failure_count": 400,
"pass_rate": 89.5,
"failed_tests": [
{"test_name": "[sig-cli] example test name", "error": "error message..."}
],
"dominant_error_patterns": [
{"pattern": "stale GroupVersion discovery: ...", "count": 50, "percentage": 12.5}
]
}Examples
Example 1: Investigate a Mass Test Failure
# Get the summary of a job run that triggered mass test failures
python3 plugins/ci/skills/fetch-job-run-summary/fetch_job_run_summary.py 2030845545290928128Example 2: Compare Two Runs
# Fetch summaries for a failing and passing run to diff
python3 plugins/ci/skills/fetch-job-run-summary/fetch_job_run_summary.py 2030845545290928128 --format json > failing.json
python3 plugins/ci/skills/fetch-job-run-summary/fetch_job_run_summary.py 2030845542774345728 --format json > passing.jsonNotes
- The
testFailureCountmay be slightly higher than the number of entries intestFailuresdue to internal deduplication - Error messages are truncated to 300 characters in text output to keep output manageable
- The dominant error pattern detection strips UUIDs and timestamps for better grouping
- For test-level output analysis (raw test failure output for a specific test across runs), use the
fetch-test-runsskill instead
See Also
- Related Skill:
fetch-test-runs- Fetch raw outputs for a specific test across multiple job runs - Related Skill:
fetch-regression-details- Fetch Component Readiness regression details - Related Skill:
ci:prow-job-analysis- Comprehensive analysis of test and install failures in a Prow job
© openshift-eng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in plugins/ci/skills/fetch-job-run-summary of openshift-eng/ai-helpers.
- SKILL.md
- fetch_job_run_summary.py
Open the folder on GitHubat commit a627176
Compare with similar skills
Fetch Job Run Summary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Fetch Job Run Summary this skillopenshift-eng/ai-helpers | 120 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Swig Testswig/swig | 6.3k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Triage CI FailureDataDog/datadog-agent | 3.8k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Fix Ready PRsfastrepl/anarlog | 9.5k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Trx Analysismicrosoft/vstest | 969 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
- Official
Triage CI Failure
DataDog/datadog-agent
Classify a failed CI as either caused by an active incident, flakiness, or a true code regression.
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Fix Ready PRs
fastrepl/anarlog
Inspect every open non-draft PR for CI failures and unresolved Cursor Bugbot findings, then fix them on the existing PR branches.
- Official
Trx Analysis
microsoft/vstest
Parse and analyze Visual Studio TRX test result files. An agent skill from microsoft/vstest.
Wio
workersio/skills
Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.
More from openshift-eng/ai-helpers
All 118 skills in this repoInvestigate CI Reliability
openshift-eng/ai-helpers
Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.
Address Review PR
openshift-eng/ai-helpers
Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.
Categorize Activity Types
openshift-eng/ai-helpers
Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.
Has Review Work
openshift-eng/ai-helpers
Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent.
Must Gather Analyzer
openshift-eng/ai-helpers
Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.
Payload Autodl JSON
openshift-eng/ai-helpers
Schema for the autodl JSON data file produced by payload-analysis for database ingestion — you must use this skill whenever generating the autodl JSON file
Related
Categories
Questions about Fetch Job Run Summary
What does Fetch Job Run Summary do?
Fetch a Prow job run summary from Sippy showing all failed tests grouped by SIG with error messages. Fetch Job Run Summary is an agent skill from openshift-eng/ai-helpers.
When should I use Fetch Job Run Summary?
Fetch Job Run Summary fits situations like: tasks that involve Failing and flaky tests.
How do I install Fetch Job Run Summary in Claude Code?
Run `npx skills add openshift-eng/ai-helpers --skill fetch-job-run-summary -a claude-code`. Or copy the skill folder (plugins/ci/skills/fetch-job-run-summary in openshift-eng/ai-helpers) into .claude/skills/fetch-job-run-summary in your project. Claude Code loads it when a task matches its description.
How do I install Fetch Job Run Summary in Codex?
Run `npx skills add openshift-eng/ai-helpers --skill fetch-job-run-summary -a codex`. Or copy the skill folder (plugins/ci/skills/fetch-job-run-summary in openshift-eng/ai-helpers) into .agents/skills/fetch-job-run-summary in your project. Codex loads it when a task matches its description.
Can I use Fetch Job Run Summary in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openshift-eng/ai-helpers --skill fetch-job-run-summary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fetch-job-run-summary, .gemini/skills/fetch-job-run-summary, .github/skills/fetch-job-run-summary and .opencode/skills/fetch-job-run-summary in your project.
What does Fetch Job Run Summary need to run?
Going by SKILL.md and its folder, Fetch Job Run Summary needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Fetch Job Run Summary access the network?
SKILL.md names 2 domains. In commands or code: sippy.dptools.openshift.org and prow.ci.openshift.org; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Fetch Job Run Summary safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Fetch Job Run Summary use?
Fetch Job Run Summary is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fetch Job Run Summary use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Fetch Job Run Summary?
Skills that share tags, products or a category with Fetch Job Run Summary: Swig Test (swig/swig, 6.3k stars), Triage CI Failure (DataDog/datadog-agent, 3.8k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars) and Fix Ready PRs (fastrepl/anarlog, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fetch Job Run Summary?
openshift-eng (a GitHub organization) maintains it in openshift-eng/ai-helpers, which has 120 GitHub stars. The repository holds 118 skills in this directory. The repository was last updated on October 6, 2026.
Source: openshift-eng/ai-helpers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.