skills.rest
openshift-eng
openshift-engOFFICIAL
Explore all skills by this author →
WebsiteGitHub

microshift-ci:create-bugs

Create USHIFT JIRA bug issues from MicroShift CI failure reports with dry-run default.

7|15|Updated Jan 23, 2026
Search Tags:#automation#mcp#deduplication#jira#bug creation#ci failure triage#microshift
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-ci-create-bugs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microshift-ci:create-bugs
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/microshift-ci/skills/create-bugs
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-ci-create-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill turns MicroShift CI failure analysis reports into actionable JIRA bug reports, preventing duplicate issues across multiple releases while avoiding accidental creation by default.

Core Features & Use Cases

  • Dry-run by default with safe previews: Show which bugs would be created without creating anything unless you explicitly add --create.
  • Cross-release deduplication: Fuzzy-match failure root causes across multiple sources so the same issue becomes a single candidate referencing all affected releases.
  • Jira-aware duplicate and regression handling: Searches for existing open duplicates, detects potential regressions from closed/verified bugs, and can link to or reopen issues in interactive mode.

Quick Start

Use the skill to preview bug candidates from release analysis by running the command: /microshift-ci:create-bugs 4.22

Frequently Asked Questions about microshift-ci:create-bugs

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

FAQPage Schema
How do I create JIRA bugs from MicroShift CI failure reports?▼

This skill creates USHIFT JIRA Bug issues from MicroShift CI analyze-ci failure reports by parsing structured summary job analysis files. It processes release-version, PR-number, and rebase-PR shorthand inputs from an existing computed workdir.

How does bug deduplication work across multiple MicroShift releases?▼

Deduplication uses Jira MCP tools for keyword and test-id searches to fuzzy-match failure root causes across multiple releases and sources. The same issue becomes a single candidate referencing all affected releases.

Does creating JIRA bugs require a dry-run first?▼

JIRA bug creation is dry-run by default, showing which bugs would be created without actually creating anything. You must explicitly add the --create flag to generate issues in JIRA.

Can I detect regression issues from closed JIRA bugs during CI failure triage?▼

The skill detects potential regressions from closed or verified JIRA bugs during triage. In interactive mode, it can link to or reopen existing issues when handling duplicates.

What input formats are supported for MicroShift CI bug creation?▼

The skill accepts release-version, PR-number, and rebase-PR shorthand inputs. It requires structured summary blocks from job analysis files that already exist in a computed workdir.

Related Skills

Explore More Software Engineering Skills→
openshift-engopenshift-eng
7

microshift-ci:doctor-refresh

Regenerate the MicroShift CI Doctor HTML report from existing bug mapping JSON files.

Official
Basic
jimwellerjimweller

Jira Release Draft

Generate draft Jira release notes grouped by issue type into markdown.

Community
Intermediate
EstomEstom

atlassian-mcp

Integrate Jira and Confluence with MCP servers for automated issue triage and page creation.

Community
Advanced
openshift-engopenshift-eng
112

Create Release Note

Generate Jira release notes from bug descriptions and linked GitHub PRs.

Community
Advanced