jira-defect-flow

Coordinate Jira defect handling from intake to pull request and tracker update.

15|5|Updated May 4, 2026
One-click install
npx skills add https://github.com/eugenelim/agent-ready-repo --skill jira-defect-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-defect-flow
Source: https://github.com/eugenelim/agent-ready-repo/tree/main/packs/atlassian/.apm/skills/jira-defect-flow
Command: npx skills add https://github.com/eugenelim/agent-ready-repo --skill jira-defect-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill turns a Jira defect ticket into a disciplined end-to-end delivery flow, so an agent can intake the issue, verify it is actionable, fix the root cause, and loop the result back to the tracker without skipping gates.

Core Features & Use Cases

  • Defect intake and triage: Reads the Jira issue, checks for environment details, reproduction steps, and expected-versus-actual behavior, then stops and asks for missing information when the ticket is incomplete.
  • Structured fix handoff: Records a triage brief, coordinates a reproduction-first bug-fix workflow, and keeps the repair focused on the smallest safe change with regression coverage.
  • Release coordination: Creates a deterministic branch name, opens a PR with the Jira key in the closing footer, posts the PR back to Jira, and advances the ticket through the correct transition.
  • Deployment-aware follow-through: Optionally runs a repo-provided dev deploy hook and updates Jira again so the defect can move toward QA without guessing at environment-specific commands.

Quick Start

Use the jira-defect-flow skill to take Jira ticket PROJ-123 from intake through triage, fix, pull request, and Jira update.

Frequently Asked Questions about jira-defect-flow

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

FAQPage Schema
How do I automate Jira bug fix workflow from ticket intake to pull request?

To automate a Jira bug fix workflow, the Skill reads the issue, validates reproduction steps, coordinates the fix, opens a pull request with a Closes footer, and updates the tracker. It enforces triage gates and deterministic branch naming end to end.

What happens if a Jira defect ticket is missing reproduction steps or environment details?

When a Jira defect ticket lacks reproduction steps or environment details, the Skill stops and asks the user for the missing information before proceeding. This ensures the issue is actionable and verifiable before any fix is attempted.

How to link a Jira issue to a GitHub pull request automatically?

To link a Jira issue to a GitHub pull request, the Skill creates a deterministic branch name and adds the Jira key in the PR closing footer. It then posts the PR back to the Jira ticket and advances the issue through the correct transition.

Can I trigger a dev deploy hook after fixing a Jira bug?

Yes, you can trigger a dev deploy hook after fixing a Jira bug. The Skill optionally runs a repo-provided deployment hook and updates Jira again so the defect can move toward QA without manual environment-specific commands.

Does the Jira defect workflow require regression coverage for bug fixes?

The Jira defect workflow requires regression coverage for bug fixes. It coordinates a reproduction-first approach and keeps the repair focused on the smallest safe change while ensuring regression tests are included.

What is the best way to triage Jira defects before writing code?

The best way to triage Jira defects before coding is to verify expected-versus-actual behavior and check for complete environment details. The Skill records a triage brief and stops to ask for missing information when the ticket is incomplete.