skills.rest
ignission
ignissionOFFICIAL
Explore all skills by this author →
WebsiteGitHub

merge-and-cleanup

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

2|Updated Jan 14, 2026
Search Tags:#automation#git#workflow#jira#pull-request#merge-pr
One-click install
npx skills add https://github.com/ignission/claude-code-ark --skill merge-and-cleanup-ignission
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-and-cleanup
Source: https://github.com/ignission/claude-code-ark/tree/main/.claude/skills/merge-and-cleanup
Command: npx skills add https://github.com/ignission/claude-code-ark --skill merge-and-cleanup-ignission

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end PR cleanup workflow by merging the pull request, syncing the main branch, and closing the related Jira ticket, reducing manual coordination.

Core Features & Use Cases

  • End-to-end workflow: Merges a PR, updates the main branch, and completes the Jira ticket with minimal user input.
  • Safety checks: Ensures only the intended PR is merged and verifies the main branch is up to date before closure.
  • Audit trail: Reports PR number and Jira ticket status changes for traceability.

Quick Start

Run this skill to merge the PR, update the main branch, and close the related Jira ticket in a single automated workflow.

Frequently Asked Questions about merge-and-cleanup

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

FAQPage Schema
How do I automate pull request merge and Jira ticket closure together?▼

Automating pull request merge and Jira ticket closure requires a workflow that merges the PR, syncs the main branch, and transitions the Jira ticket. This skill coordinates git operations and Jira issue transitions with basic safety checks to ensure the intended PR is merged before closure.

Can I sync the main branch automatically after merging a pull request?▼

Yes, syncing the main branch automatically after merging a pull request is a core part of this workflow. The skill updates the main branch and verifies it is up to date before proceeding to close the related Jira ticket.

What is the best way to transition multiple Jira tickets after a git merge?▼

Transitioning multiple Jira tickets after a git merge is handled by parameterizing PR and Jira identifiers within an automated workflow. This skill applies safety checks to coordinate git operations and Jira issue transitions for multiple tickets.

Does this PR merge workflow include safety checks before closing Jira issues?▼

Yes, the PR merge workflow includes safety checks before closing Jira issues. It ensures only the intended PR is merged and verifies the main branch is up to date before transitioning the related Jira ticket to closure.

How do I trace Jira ticket status changes during an automated git workflow?▼

Tracing Jira ticket status changes during an automated git workflow is achieved through audit reporting. This skill reports PR numbers and Jira ticket status changes to provide traceability for the end-to-end cleanup process.

Related Skills

Explore More Software Engineering Skills→
taloncjonestaloncjones

post-merge

Remove Git worktrees and branches, then update linked Jira tickets.

Community
Advanced
CODE-SAURABHCODE-SAURABH
2

release-engineer

Coordinate software releases from code review through production deployment and rollback readiness.

Community
Advanced
aberrantCodeaberrantCode
1

ship-to-dev

Merge feature branches into DEV after passing tests and coverage gates.

Community
Advanced
namuannamuan
4

ticket-mode

Automates Jira ticket-to-GitHub-PR workflows including polling, branching, and PR generation.

Community
Advanced