What problem does it solve? Fixing a JIRA bug often means jumping between the issue tracker, the codebase, and git without a disciplined process, leading to unverified root causes, scope creep, and accidental pushes. This Skill enforces a gated workflow that requires stable reproduction, evidence-backed root-cause analysis, and explicit user approval before any code edit or local commit. ## Core Features & Use Cases - Read-only JIRA integration: Query issue details, comments, and same-origin attachments via a Python script using skill-local .env credentials, with no writes to JIRA. - Pyramid review summaries: Present findings top-down with a review conclusion, business reproduction chain, root-cause summary, and recommended solution, using Mermaid diagrams where they clarify causal chains. - Gated fix workflow: Reproduce the failure at least twice, add a failing regression test before the fix, self-review against a code-review checklist, and create a local commit containing the exact JIRA key—never pushing or opening a merge request. - Use Case: A developer receives JIRA-1234 reporting a pricing bug. The Skill reads the issue, reproduces the failure twice, presents a Mermaid-illustrated root-cause review for approval, adds a regression test, implements the minimal fix, and creates a local commit like fix(order): JIRA-1234 修复折扣状态丢失. ## Quick Start Ask the agent to use the jira-auto-fix skill to reproduce and diagnose JIRA-1234, present a pyramid review with a Mermaid diagram, then fix and locally commit after your approvals.
