skills.rest
tigredonorte
tigredonorteCOMMUNITY
Explore all skills by this author →
GitHub

transition-testing

Verify Jira In Testing tasks have merged pull requests and propose transitions to Done.

Updated Feb 25, 2026
Search Tags:#automation#workflow#devops#analysis#jira#pull-request#transition
One-click install
npx skills add https://github.com/tigredonorte/claude-plugin-work --skill transition-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: transition-testing
Source: https://github.com/tigredonorte/claude-plugin-work/tree/main/skills/transition-testing
Command: npx skills add https://github.com/tigredonorte/claude-plugin-work --skill transition-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically verifies Jira tasks labeled In Testing have corresponding merged pull requests and prompts for safe transitions to Done, reducing manual checks and delays.

Core Features & Use Cases

  • Validate that each In Testing task has a merged PR referencing the ticket.
  • Verify that the merge is present in the main branch history before transitioning.
  • Prompt for user confirmation before transitioning any tasks and support exclusions for selective updates.
  • Supports multi-task orchestration across multiple Jira issues in parallel.

Quick Start

Run /transition-testing to verify your In Testing tasks and propose transitions for merged PRs.

Frequently Asked Questions about transition-testing

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

FAQPage Schema
How do I automate Jira task transitions after a pull request merges?▼

You can automate Jira task transitions by running a workflow that verifies merged pull requests and proposes moving In Testing tickets to Done. The process checks if the merge exists in the main branch history before prompting for user confirmation to finalize the transition.

Can I verify multiple Jira issues in parallel before transitioning them to Done?▼

Yes, this workflow supports multi-task orchestration across multiple Jira issues in parallel. It validates that each In Testing task has a corresponding merged PR referencing the ticket before proposing any transitions.

Do I need integrated GitHub and Jira tooling to automate PR verification for ticket transitions?▼

Yes, you need integrated access to both Jira and GitHub to perform PR verification and task transitions. The workflow queries GitHub for merged pull requests and Jira for ticket status to safely propose updates.

How does Jira workflow automation handle selective task updates and exclusions?▼

Jira workflow automation handles selective updates by prompting for user confirmation before transitioning any tasks. You can apply exclusions to skip specific tickets, ensuring only verified In Testing issues with merged PRs are moved to Done.

Why are my In Testing Jira tasks not transitioning when a pull request is merged?▼

In Testing Jira tasks fail to transition automatically if the merged pull request is not present in the main branch history or lacks a ticket reference. The workflow requires explicit user confirmation after verifying these conditions before proposing a transition to Done.

Related Skills

Explore More Software Engineering Skills→
adobecomadobecom
1

sync-pr-jira

Automates synchronization of GitHub pull request statuses with Jira ticket statuses.

Official
Intermediate
luigiinredluigiinred
1

release-ticket-report

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

Community
Intermediate
vince-winkintelvince-winkintel
43

glab-ci

Manage GitLab CI/CD pipelines, jobs, and artifacts.

Community
Intermediate
skillcreatoraiskillcreatorai
1.1k

jira-issues

Create, update, and track Jira issues via the REST API.

Community
Advanced