Jira Pull Request Extractor

Jira Pull Request Extractor is a skill for Claude Code, Codex from wangke19/gemini-ai-helpers. It costs 18 tokens per session (2,232 once invoked), scanned A, a copy of extract-prs, Apache-2.0.

A tool procedure that finds GitHub pull request links connected to a Jira issue and its child issues. Jira is used to track work, and GitHub pull requests are proposed code changes.

In plain words
What is it for?
It helps create a complete list of pull requests for a feature, release documentation, or change tracking.
Why use it?
It avoids searching through Jira descriptions, comments, and linked records by hand, while removing duplicate links.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps create a complete list of pull requests for a feature, release documentation, or change tracking.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wangke19/gemini-ai-helpers/extract-prs
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add wangke19/gemini-ai-helpers --skill extract-prs
Clone the repo
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpers

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for Jira Pull Request Extractor

README.md
[![agentmods](https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/extract-prs/github.svg)](https://agentmods.dev/skills/wangke19/gemini-ai-helpers/extract-prs)
Your own site
<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/extract-prs"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/extract-prs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for Jira Pull Request Extractor

Your own site · 80×15
<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/extract-prs"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/extract-prs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,232 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.02232
Opus 5 $0.00009 $0.01116
Sonnet 5 $0.00004 $0.00446
Haiku 4.5 $0.00002 $0.00223

Measured 7d ago against content hash 05f132ba1247, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

Jira Pull Request Extractor scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Uses MCP authentication (no separate curl needed)
Origin

This is a copy

91% identical to extract-prs — 77 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

extensions/jira/skills/extract-prs/SKILL.md · 205 lines

How it starts

The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Jira Pull Request Extractor

This skill recursively discovers Jira issues and extracts all associated GitHub Pull Request links.

IMPORTANT FOR AI: This is a procedural skill - when invoked, you should directly execute the implementation steps defined in this document. Do NOT look for or execute external scripts (like extract_prs.py). Follow the step-by-step instructions in the "Implementation" section below.

When to Use This Skill

Use this skill when you need to:

  • Discover all GitHub PRs associated with a Jira feature and its subtasks
  • Extract PR metadata without analyzing PR content
  • Build a complete map of PRs for documentation or release notes

Key characteristics:

  • Always recursive: Automatically discovers all descendant issues via childIssuesOf() JQL
  • PR-only: Extracts only Pull Request URLs (ignores Issue and Commit URLs)
  • Dual-source: Extracts from both changelog remote links and text content (description/comments)
  • Structured output: Returns JSON with PR metadata and deduplication across sources

Prerequisites

  • MCP Jira server configured and running (required - see extensions/jira/README.md for setup)
  • jq installed for JSON parsing
  • GitHub CLI (gh) installed and authenticated for fetching PR metadata
  • User has read permissions for target Jira issues (including private issues via MCP authentication)
  • User has read access to linked GitHub repositories

Output Format

Purpose: This skill returns structured JSON that serves as an interface contract for consuming skills and commands.

Delivery Method:

  • Primary: Output JSON directly to the response (no file writes, no user prompts)
  • Secondary: Only save to .work/extract-prs/{issue-key}/output.json if user explicitly requests to save results

Schema Version: 1.0

Structure

{
  "schema_version": "1.0",
  "metadata": {
    "generated_at": "2025-11-24T10:30:00Z",
    "command": "extract_prs",
    "input_issue": "OCPSTRAT-1612"
  },
  "pull_requests": [
    {
      "url": "https://github.com/openshift/hypershift/pull/6444",
      "state": "MERGED",
      "title": "Add support for custom OVN subnets",
      "isDraft": false,
      "sources": ["comment", "description", "remote_link"],
      "found_in_issues": ["CNTRLPLANE-1201", "OCPSTRAT-1612"]
    }
  ]
}

Read the full file on GitHub · 205 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 205 lines · 18 tokens per session scan A 05f132ba1247

Subscribe to this mod's changes

Jira Pull Request Extractor is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 2,232 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to extract-prs, differing in 77 lines, and is treated as a copy.

Related

Other skills, from other repositories

lov-rename-project

A project-renaming workflow that updates a product or repository name across source files, configuration, and documentation. It produces a reviewable plan and preserves compatibility-sensitive names and references where needed.

lovstudio/skills · 45 tokens

lov-gh-tidy

Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…

lovstudio/skills · 95 tokens

lov-checkpoint

A project checkpoint tool that records what changed, what was verified, unresolved work, and the next steps using Git status and history. Git is the system that tracks changes to project files.

lovstudio/skills · 38 tokens

github-issues

Manage GitHub issues with gh: confirm repo and state, deduplicate, preserve evidence, and verify authorized creation, edits, labels, comments, or closure.

fmind/dotfiles · 36 tokens

project-flow-ops

Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.

Jamkris/everything-gemini-code · 59 tokens

ship-issue

End-to-end conductor that drives a single GitHub issue all the way to a merged PR. Chains the issue-workflow skills — sync the base branch, analyze the issue, implement a minimal fix with a test, open a PR, drive CI to green, confirm the merge, run post-merge cleanup, and wrap up. Use to take one issue from a cold…

jerseycheese/agent-skills · 91 tokens