triage

Triage Jira issues for RHEL packages to determine rebase, backport, rebuild, or clarification paths.

28|36|Updated Jun 17, 2025
One-click install
npx skills add https://github.com/packit/ai-workflows --skill triage-packit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/packit/ai-workflows/tree/main/agents_as_skills/triage
Command: npx skills add https://github.com/packit/ai-workflows --skill triage-packit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage Jira issues for RHEL packages to determine the appropriate resolution path (rebase, backport, rebuild, or clarification) and prepare CVE applicability assessments before reporting back to Jira.

Core Features & Use Cases

  • Automatic CVE eligibility checks and resolution routing for Jira issues.
  • Patch URL validation, patch management, and target branch determination.
  • Consolidation of rebuild siblings and Jira comment automation for streamlined workflow.

Quick Start

Provide the Jira issue key to start triage.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I triage Jira issues to decide between rebase and backport for RHEL packages?

Triage Jira issues for RHEL packages by analyzing the issue context to determine the appropriate resolution path: rebase, backport a patch, rebuild, or request clarification. Provide the Jira issue key to start the automated resolution routing process.

Can I check CVE applicability and validate patch URLs for dist-git branches automatically?

Yes, CVE applicability checks and patch URL validation are performed automatically across dist-git branches. The triage process evaluates CVE eligibility and validates patch URLs before determining the target branch and reporting back to Jira.

What is the best way to consolidate rebuild siblings and automate Jira commenting during triage?

Consolidate rebuild siblings and automate Jira commenting by running the triage process on the Jira issue. It automatically groups related rebuilds and posts resolution comments directly to Jira to streamline the workflow.

Does the triage process support dry-run and silent modes for RHEL package issues?

Yes, the triage process supports both dry-run and silent modes. Dry-run allows you to preview the determination of rebase, backport, or rebuild actions without making changes, while silent mode suppresses automated Jira commenting.

When should I request clarification instead of backporting a patch during Jira issue triage?

Request clarification when the triage process cannot determine a clear resolution path for the RHEL package issue. This occurs when the issue context, CVE applicability, or dependency changes across dist-git branches lack sufficient detail to rebase or backport.