skills.rest
darellchua2
darellchua2COMMUNITY
Explore all skills by this author →
Website𝕏@DarellChua2GitHub

jira-status-updater

Automates JetPA ticket status updates to Done or Closed after PR merges via Atlassian APIs.

4|4|Updated Jan 15, 2026
Search Tags:#automation#workflow#devops#jira#atlassian#pull-request#transition
One-click install
npx skills add https://github.com/darellchua2/opencode-config-template --skill jira-status-updater
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-status-updater
Source: https://github.com/darellchua2/opencode-config-template/tree/main/skills/jira-status-updater
Command: npx skills add https://github.com/darellchua2/opencode-config-template --skill jira-status-updater

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates post-PR merge workflow by updating JIRA ticket status to reflect completed work, ensuring issue closure and traceability.

Core Features & Use Cases

  • Detects linked JIRA ticket from PR title, branch name, or merge commit
  • Fetches available status transitions from Atlassian API and selects final statuses (Done/Closed)
  • Executes the transition and posts a detailed merge summary comment

Quick Start

Run jira-status-updater with the ticket key and cloud ID to transition the ticket to the final status after a PR merge. Example: jira-status-updater --ticket IBIS-101 --cloudId <CLOUD_ID> --target-status Done

Frequently Asked Questions about jira-status-updater

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

FAQPage Schema
How do I automatically transition JIRA tickets to Done when a pull request is merged?▼

To automatically transition JIRA tickets to Done when a pull request is merged, this Skill uses Atlassian APIs to detect the linked ticket, fetches available workflow transitions, executes the final status update, and posts a merge summary comment for auditing.

How does automated JIRA status update after a PR merge detect which ticket to close?▼

Automated JIRA status updates after a PR merge detect the target ticket by parsing the pull request title, branch name, or merge commit to identify the corresponding JIRA work item key before applying any workflow transitions.

Do I need specific Atlassian permissions to automate JIRA ticket transitions after a PR merge?▼

Yes, automating JIRA ticket transitions after a PR merge requires Atlassian cloud access and appropriate API permissions to query existing ticket statuses, retrieve available workflow transitions, and execute status updates to Done or Closed.

What is the best way to ensure traceability when closing JIRA issues via pull request merges?▼

The best way to ensure traceability when closing JIRA issues via pull request merges is to automate the workflow transition and post a detailed merge summary comment on the ticket, creating an auditable record of the completed development work.

Can I choose a specific target status like Closed or Done when automating JIRA ticket updates?▼

Yes, you can choose a specific target status like Closed or Done when automating JIRA ticket updates; the Skill fetches all available transitions from the Atlassian API and applies the selected final status to reflect the completed pull request work.

Related Skills

Explore More Software Engineering Skills→
darellchua2darellchua2
4

jira-git-integration

Create Jira issues, add comments, upload attachments, and generate branch names from ticket keys.

Community
Intermediate
KirKruglovKirKruglov
5

monitor-progress

Generate sprint progress, deviation, and weekly status reports from Jira and planning data.

Community
Intermediate
ferstarferstar

glab

Automate GitLab workflows via CLI for issues, merge requests, and pipelines.

Community
Advanced
stephanjstephanj
9

jira

Manage Jira issues and sprints via natural language commands.

Community
Advanced