skills.rest
akshatdalton
akshatdaltonCOMMUNITY
Explore all skills by this author β†’
𝕏@DaltonAkshatGitHub

ship-task

Orchestrate Jira ticket shipping through implementation, PR submission, and CI monitoring.

Updated Apr 6, 2026
Search Tags:#Jira#CI monitoring#end-to-end workflow#ticket shipping#PR handling
One-click install
npx skills add https://github.com/akshatdalton/skills --skill ship-task-akshatdalton
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: ship-task
Source: https://github.com/akshatdalton/skills/tree/main/ship-task
Command: npx skills add https://github.com/akshatdalton/skills --skill ship-task-akshatdalton

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Manages the end-to-end shipping of a Jira ticket, from work-in-progress to merged code, through a streamlined process that includes CI watch loops and automated PR handling.

Core Features & Use Cases

  • Jira Ticket Shipping: Orchestrates ticket shipping by routing through predefined steps including task execution, PR creation, and CI monitoring.
  • CI Watch Loop: Monitors the continuous integration status of the PR and applies fixes automatically.
  • User Input Handling: Stops only on specific user-input criteria and allows manual intervention where needed.
  • Use Case: Ideal for developers or project managers looking to automate the complete process of moving a ticket through Jira to the final merge.

Quick Start

Use the ship-task skill with a Jira ticket number to automatically begin shipping the ticket, e.g., 'ship-task ENG-XXXXX'.

Frequently Asked Questions about ship-task

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

FAQPage Schema
How do I automate Jira ticket shipping from work-in-progress to a merged pull request?β–Ό

Automated Jira ticket shipping routes a ticket through implementation, PR creation, and CI monitoring to reach a merged state. The workflow stops only at designated points requiring user input for design decisions, reviewer comments, or manual intervention.

What's the best way to monitor CI status on a Jira ticket pull request and apply fixes automatically?β–Ό

Monitoring CI status on a Jira ticket pull request is handled by a continuous watch loop that tracks integration checks and applies fixes automatically. This ensures the PR meets CI requirements before proceeding to the final merge.

Can I use an automated PR handling workflow if my Jira ticket needs manual intervention at specific steps?β–Ό

Automated PR handling workflows support manual intervention by stopping only on predefined user-input criteria. You can address design decisions and reviewer comments at these designated points before the process continues toward merging.

Does the end-to-end Jira ticket workflow handle PR submission and intermediate implementation steps?β–Ό

End-to-end Jira ticket workflows handle intermediate implementation steps including task execution and PR submission. The process orchestrates the complete path from work-in-progress status through to the final merged code.

How do I start shipping a Jira ticket using a ticket number?β–Ό

Shipping a Jira ticket begins by providing the ticket number, such as 'ENG-XXXXX', to the workflow. This initializes the automated process of routing the ticket through implementation, PR handling, and CI monitoring.

Related Skills

Explore More Software Engineering Skills→
ignissionignission
2

merge-and-cleanup

Merge a pull request, sync the main branch, and close its Jira ticket.

Official
Intermediate
semicolon-devteamsemicolon-devteam

sync-project-status

Synchronize GitHub Projects statuses with Issue states via GraphQL mutations.

Official
Intermediate
drxaibidrxaibi

continuous-agent-loop

Orchestrate continuous autonomous agent loops with quality gates and recovery controls.

Community
Advanced
paulchiupaulchiu
3

linear-do

Automate Linear issue handling from ticket intake through CI monitoring.

Community
Advanced