create-jira-issue-from-pr

Convert GitHub pull request context into a JIRA issue draft.

Updated Aug 15, 2025
One-click install
npx skills add https://github.com/pekral/pekral.cz --skill create-jira-issue-from-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-jira-issue-from-pr
Source: https://github.com/pekral/pekral.cz/tree/main/.claude/skills/create-jira-issue-from-pr
Command: npx skills add https://github.com/pekral/pekral.cz --skill create-jira-issue-from-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts GitHub pull request context into a structured, JIRA-ready issue draft while preserving the original assignment wording for accuracy and alignment between technical and non-technical stakeholders.

Core Features & Use Cases

  • PR-to-Issue Drafting: Collects original assignment text plus relevant PR review context and constraints, then maps unresolved items into an implementation plan.
  • Verbatim Preservation: Keeps the original assignment text unchanged, improving traceability and reducing misunderstandings.
  • JIRA-Optimized Structure: Produces a goal summary, technical context for AI/engineers, concrete implementation requirements, and testable acceptance criteria.

Quick Start

Ask the AI to create a JIRA issue draft from the provided GitHub PR URL and return a markdown output formatted for JIRA with the original assignment text included verbatim.

Frequently Asked Questions about create-jira-issue-from-pr

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

FAQPage Schema
How do I convert a GitHub pull request into a JIRA issue draft?

To convert a GitHub pull request into a JIRA issue draft, the tool collects original assignment text and PR review context, maps unresolved items to implementation requirements, and produces testable acceptance criteria formatted for JIRA.

What is requirements mapping from a pull request to JIRA?

Requirements mapping from a pull request to JIRA is the process of transforming unresolved PR review comments and constraints into concrete implementation tasks and testable acceptance criteria within a JIRA-ready issue draft.

How do I preserve original assignment text when creating a JIRA issue from a PR?

To preserve original assignment text when creating a JIRA issue from a PR, the tool keeps the verbatim assignment wording unchanged, ensuring traceability and reducing misunderstandings between technical and non-technical stakeholders.

Do I need GitHub CLI and JIRA CLI to draft issues from pull requests?

You do not strictly need GitHub CLI and JIRA CLI to draft issues from pull requests, but the tool prefers them for automated context collection, with MCP fallback mechanisms available for environments lacking direct CLI access.

What is included in a JIRA issue draft generated from a PR?

A JIRA issue draft generated from a PR includes a goal summary, technical context for engineers, verbatim original assignment text, concrete implementation requirements, and testable acceptance criteria derived from review findings.

Can I map unresolved PR review comments to JIRA acceptance criteria?

Yes, you can map unresolved PR review comments to JIRA acceptance criteria by having the tool analyze the PR review context and constraints, transforming those unresolved findings into testable requirements for the implementation plan.