two-node:create-rhel-stories

Create OCPEDGE backlog stories from grouped RHEL TNF verification tickets via Jira.

7|15|Updated Jan 23, 2026

Search Tags:#automation #jira #subtasks #story creation #jql search #ticket linking #rhel verification

Ready to run

npx skills add https://github.com/openshift-eng/edge-tooling --skill two-node-create-rhel-stories

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: two-node:create-rhel-stories
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/two-node/skills/create-rhel-stories
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill two-node-create-rhel-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It eliminates the manual effort of finding untested RHEL TNF verification tickets, grouping related issues, creating missing OCPEDGE backlog stories, and linking the tickets with the correct components.

Core Features & Use Cases

Auto-discover or target RHEL tickets: Use specific RHEL ticket keys or run a JQL query (or the default JQL) to discover untested TNF resource-agents tickets.
Deterministic grouping and story generation: Groups related tickets using ticket summaries, clone relationships, and shared references, then generates consistent Jira-ready summaries and descriptions.
Safe, user-confirmed Jira changes: Runs a dry-run plan, requires explicit approval, creates OCPEDGE stories and subtasks, and links RHEL tickets to the stories.

Quick Start

Use the two-node:create-rhel-stories skill to preview and create OCPEDGE stories for untested TNF resource-agents RHEL tickets by running /two-node:create-rhel-stories --dry-run and then confirming the plan.

Frequently Asked Questions about two-node:create-rhel-stories

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

FAQPage Schema

How do I automate OCPEDGE story creation from RHEL verification tickets?▼

Automating OCPEDGE story creation from RHEL verification tickets involves grouping related issues, generating summaries, and creating missing backlog stories using a JQL query or specific ticket keys.

How does grouping related RHEL tickets for Jira story creation work?▼

Grouping related RHEL tickets works by parsing ticket summaries, clone relationships, and shared references to deterministically cluster issues before generating consistent Jira-ready OCPEDGE stories and descriptions.

Can I preview Jira story creation for TNF RHEL tickets before applying changes?▼

Yes, you can preview Jira story creation for TNF RHEL tickets by running the command with the --dry-run flag, which generates a planning overview that requires explicit approval before creating any OCPEDGE stories or subtasks.

Do I need Jira access to create OCPEDGE stories for RHEL tickets?▼

Yes, you need Jira access configured via the mcp-atlassian MCP tools to search RHEL tickets, assign components, create verification and automation subtasks, and add Relates links between the tickets and stories.

What is the best way to link untested RHEL TNF tickets to OCPEDGE backlog stories?▼

The best way to link untested RHEL TNF tickets to OCPEDGE backlog stories is to use an automated workflow that detects missing stories, groups tickets by shared references, and applies Relates links during the story creation process.

Why are my RHEL TNF verification tickets missing OCPEDGE backlog stories?▼

RHEL TNF verification tickets may be missing OCPEDGE backlog stories because they have not been grouped and processed by the story creation workflow, which detects untested tickets and generates the required parent stories and subtasks.