Triage Regression

Creates or updates Component Readiness triage records via the Sippy API to link regressions with a JIRA bug.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/openshift-eng/ga-regression-reports --skill triage-regression
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Triage Regression
Source: https://github.com/openshift-eng/ga-regression-reports/tree/main/.claude/skills/triage-regression
Command: npx skills add https://github.com/openshift-eng/ga-regression-reports --skill triage-regression

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or update a Component Readiness triage record to link one or more regressions to a JIRA bug, enabling teams to track root causes and triage progress.

Core Features & Use Cases

  • Create a new triage for one or more regressions
  • Update an existing triage to add regressions or modify details
  • Authenticate to sippy-auth using a Bearer token
  • Validate triage type locally before making the API call
  • Supports product, test, ci-infra, and product-infra triage types

Quick Start

Run the triage_regression.py script with one or more regression IDs, a token, a Jira URL, and a triage type to create a new triage.

Frequently Asked Questions about Triage Regression

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

FAQPage Schema
How do I link Component Readiness regressions to a JIRA bug?

To link Component Readiness regressions to a JIRA bug, you create or update a triage record using the Sippy API by providing regression IDs, a JIRA URL, and a valid triage type.

What triage types are supported for linking OpenShift regressions?

Supported triage types for linking OpenShift regressions include product, test, ci-infra, and product-infra. The triage type is validated locally before the Sippy API call is made.

Do I need an authentication token to create a regression triage record?

Yes, you need a Bearer token to authenticate with sippy-auth before creating or updating a regression triage record via the Sippy API.

Can I update an existing triage record to add more regressions without losing data?

Yes, updating an existing triage record adds regressions or modifies details while preserving the existing triage state, ensuring no previous triage data is lost during the update.

What's the best way to batch multiple regression IDs into a single JIRA triage?

To batch multiple regression IDs into a single JIRA triage, run the triage_regression script with multiple regression IDs, a JIRA URL, and an optional description to group them under one record.

Why does my regression triage update fail before reaching the Sippy API?

A regression triage update fails locally before reaching the Sippy API if the provided triage type is not one of the supported types or if the Bearer token authentication is missing.