Jira Pull Request Extractor

Discover Jira issues recursively and extract GitHub Pull Request links into deduplicated JSON.

112|305|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/openshift-eng/ai-helpers --skill jira-pull-request-extractor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Jira Pull Request Extractor
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/jira/skills/extract-prs
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill jira-pull-request-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, gh.

What problem does it solve?

This Skill eliminates the manual effort of tracking down all GitHub Pull Requests associated with Jira features and their subtasks, ensuring complete release documentation.

Core Features & Use Cases

  • Recursive Discovery: Automatically finds all descendant issues using Jira's built-in childIssuesOf() function.
  • Dual-Source Extraction: Extracts PR URLs from both Jira remote links and text content (descriptions/comments).
  • Structured Output: Returns clean JSON with PR metadata, deduplication, and source tracking.
  • Use Case: When preparing release notes for feature OCPSTRAT-1612, use this Skill to automatically discover all 15+ PRs across its stories and subtasks.

Quick Start

Use the Jira Pull Request Extractor skill to find all GitHub PRs linked to Jira issue OCPSTRAT-1612.

Frequently Asked Questions about Jira Pull Request Extractor

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

FAQPage Schema
How do I extract all GitHub pull requests linked to a Jira issue and its subtasks?

The Jira Pull Request Extractor recursively discovers Jira issues and their descendants, then extracts all associated GitHub PR links from descriptions, comments, and remote links, outputting a deduplicated JSON map of PR metadata for complete release documentation.

Can I automatically find pull requests across Jira epics, stories, and subtasks?

Yes. This Skill uses Jira's childIssuesOf() function to recursively discover all descendant issues, then extracts PR URLs from both remote links and text content across the entire issue hierarchy in a single operation.

What are the prerequisites for using GitHub PR extraction with Jira?

You need an MCP Jira server configured, jq for JSON processing, and GitHub CLI (gh) installed to authenticate and fetch PR metadata. The Skill then recursively queries Jira and extracts PR links from all sources.

How do I prepare release notes by collecting all PRs from a Jira feature?

Point this Skill at your root Jira issue—it automatically discovers all related stories and subtasks, extracts every linked GitHub PR, and returns structured JSON with PR metadata and source tracking for release documentation.

Does this work with remote issue links and inline PR mentions in Jira comments?

Yes. The Skill applies dual-source extraction, pulling PR URLs from both Jira remote links and text content in issue descriptions and comments, then deduplicates the results into a single JSON output.

What output format does the PR extraction provide?

The Skill returns clean, deduplicated JSON containing PR metadata with source tracking, so you can trace where each pull request link originated in your Jira issue tree.