release-ticket-report

Compare the latest GitHub release with Jira's 'Merged' column to identify tickets needing 'Done' status.

1|Updated Feb 18, 2026

Search Tags:#workflow automation #github #ticket management #release #reporting #jira

Ready to run

npx skills add https://github.com/luigiinred/dotfiles --skill release-ticket-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-ticket-report
Source: https://github.com/luigiinred/dotfiles/tree/main/dot_cursor/skills/release-ticket-report
Command: npx skills add https://github.com/luigiinred/dotfiles --skill release-ticket-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, acli, jq, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of comparing GitHub releases with Jira tickets, identifying discrepancies and ensuring all released items are properly marked as 'Done' in Jira.

Core Features & Use Cases

Release vs. Jira Comparison: Cross-references tickets in the latest GitHub release with those in the Jira 'Merged' column.
Identify Actionable Items: Clearly lists tickets that were released but not transitioned to 'Done' in Jira.
Pending Release Tracking: Shows tickets that are merged but not yet released.
Use Case: Before a production release, use this Skill to quickly verify that all tickets intended for the release are accounted for and to identify any that need a final status update in Jira.

Quick Start

Generate a report comparing the latest GitHub release with the Jira board's Merged column.

Frequently Asked Questions about release-ticket-report

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

FAQPage Schema

How do I generate a release readiness report comparing GitHub releases with Jira tickets?▼

Generate a release readiness report by comparing the latest GitHub release with the Jira board's 'Merged' column to identify tickets requiring a status transition to 'Done'. It cross-references GitHub and Jira to highlight discrepancies and pending items.

How do I find Jira tickets that are merged but not transitioned to Done after a GitHub release?▼

Identify merged Jira tickets not transitioned to 'Done' by cross-referencing the latest GitHub release with the Jira board. The report lists actionable items that need a final status update in Jira using the Jira API.

Do I need GitHub CLI and acli installed to automate Jira release tracking?▼

Yes, you need GitHub CLI (gh) and acli installed to automate Jira release tracking. These dependencies handle data retrieval from GitHub releases and Jira boards, while jq processes the JSON data for the report.

Can I automatically update Jira ticket statuses based on a GitHub release?▼

Yes, you can update Jira ticket statuses based on a GitHub release. The Skill identifies tickets in the 'Merged' column that match the release and utilizes the Jira API to transition their status to 'Done'.

What is the best way to track pending releases in Jira before a production deployment?▼

Track pending releases in Jira by generating a report that shows tickets currently in the 'Merged' column but not yet included in a GitHub release. This verifies all intended items are accounted for before deployment.

Why does my Jira board still show tickets as Merged after a GitHub release?▼

Jira board tickets remain 'Merged' after a GitHub release when status transitions are missed. The report identifies these discrepancies by comparing the release with the Jira board to pinpoint tickets needing manual or automated updates.