How do I authenticate this skill with my JIRA instance?

You must set the JIRA_URL and JIRA_PERSONAL_TOKEN environment variables. You can generate a personal access token within your JIRA profile settings.

Can I analyze multiple components at once?

Yes, you can provide a space-separated list of component names using the --component argument to get a comparative breakdown.

Does this skill include closed or resolved bugs?

By default, it includes bugs closed within the last 30 days to help track velocity. You can also use the --include-closed flag to view older resolved issues.

What is the maximum number of JIRA issues this skill can summarize?

The skill defaults to 100 issues for speed, but you can increase this up to 1000 using the --limit parameter for more comprehensive data analysis.

JIRA Backlog Summarizer

Name: JIRA Backlog Summarizer
Author: openshift-eng

byopenshift-eng

•

Analytics & Monitoring

Analyzes and summarizes JIRA bug reports to provide comprehensive project-wide and component-specific health metrics.

About

The Summarize JIRAs skill provides automated insights into your JIRA backlog by querying and categorizing bugs across specific projects and components. It transforms raw ticket data into actionable statistics, including status distributions, priority levels, and velocity metrics—such as bugs opened versus closed over the last 30 days. This skill is ideal for engineering leads and developers who need to monitor component health, track bug trends, and generate rapid summary reports directly within their AI-powered workflow.

Key Features

29 GitHub stars
High-limit fetching for accurate large-scale statistics
Customizable filters for project, component, and status
Priority and status breakdown reports
Velocity tracking for opened vs. closed bugs
Multi-component bug distribution analysis

Use Cases

Monitoring triage performance by analyzing 'New' vs 'In Progress' bug counts
Assessing the stability of specific software components based on defect density
Generating automated weekly bug backlog reports for stakeholders

About

Key Features

29 GitHub stars
High-limit fetching for accurate large-scale statistics
Customizable filters for project, component, and status
Priority and status breakdown reports
Velocity tracking for opened vs. closed bugs
Multi-component bug distribution analysis

Use Cases

Monitoring triage performance by analyzing 'New' vs 'In Progress' bug counts
Assessing the stability of specific software components based on defect density
Generating automated weekly bug backlog reports for stakeholders