resolve-random-jira-issue

Selects a random AI-tagged JIRA issue and delegates its resolution to a linked GitHub pull request.

Updated Aug 15, 2025

Search Tags:#code review #workflow automation #test coverage #jira #ai-assisted development #ci checks #github pull request

Ready to run

npx skills add https://github.com/pekral/pekral.cz --skill resolve-random-jira-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resolve-random-jira-issue
Source: https://github.com/pekral/pekral.cz/tree/main/.claude/skills/resolve-random-jira-issue
Command: npx skills add https://github.com/pekral/pekral.cz --skill resolve-random-jira-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, acli, JIRA MCP server.

What problem does it solve?

It reduces the effort of picking up a tagged “Resolve_by_AI” JIRA task and turning it into a completed, review-ready GitHub pull request while keeping the issue status synchronized.

Core Features & Use Cases

Random tagged issue resolution: Loads only AI-tagged, not-yet-resolved JIRA issues (e.g., tasks labeled “Resolve_by_AI”) and selects one to work on.
Automated delegated resolution with a PR guarantee: Delegates the actual fix to the resolve-jira-issue skill, then validates that a GitHub PR was created and linked back to the selected JIRA issue.
Tooling and workflow guardrails: Prefers GitHub CLI (gh) for GitHub operations, ensures the local workspace is on the latest main branch before work, and uses JIRA Wiki Markup for JIRA comments.

Quick Start

Use the resolve-random-jira-issue skill to log into JIRA, pick one not-yet-resolved “Resolve_by_AI” issue at random, delegate the resolution to resolve-jira-issue, and ensure the resulting GitHub PR is linked back to that JIRA ticket.

Frequently Asked Questions about resolve-random-jira-issue

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

FAQPage Schema

How do I automate JIRA issue resolution with a linked GitHub pull request?▼

You can automate JIRA issue resolution by selecting a tagged ticket, delegating the fix workflow, and enforcing completion through a linked GitHub pull request. This process keeps JIRA issue status synchronized with GitHub CI validation and code review.

What is the best way to pick up AI-tagged JIRA issues for automated bug fixes?▼

The best way to pick up AI-tagged JIRA issues is to load unresolved tickets labeled for AI resolution and select one at random. The workflow delegates the bug fix or refactor, ensuring a review-ready GitHub pull request is linked back to the JIRA ticket.

Do I need GitHub CLI to link a JIRA ticket to a pull request?▼

You need GitHub CLI (gh) for GitHub operations, or an available GitHub MCP fallback, to link a JIRA ticket to a pull request. The workflow requires GitHub CLI to create and link the PR back to the selected JIRA issue.

Can I use JIRA Wiki Markup for comments when automating GitHub pull request workflows?▼

Yes, you can use JIRA Wiki Markup for comments when automating GitHub pull request workflows. The workflow specifically uses JIRA Wiki Markup for JIRA comments to maintain formatting consistency during issue resolution and PR linking.

Why does my automated JIRA to GitHub workflow fail without a linked pull request?▼

Your automated JIRA to GitHub workflow fails without a linked pull request because the process enforces completion via a PR guarantee. If it cannot create and link a GitHub PR back to the JIRA issue, it stops with failure.

What are the limitations of automating JIRA issue resolution with AI?▼

Limitations include requiring an up-to-date main branch before work begins, dependency on GitHub CLI or MCP fallback, and failure if a GitHub PR cannot be created and linked. It applies to bug fixes and refactors in JIRA-to-GitHub workflows.