post-merge

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

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/taloncjones/dotfiles --skill post-merge-taloncjones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-merge
Source: https://github.com/taloncjones/dotfiles/tree/main/claude/skills/post-merge
Command: npx skills add https://github.com/taloncjones/dotfiles --skill post-merge-taloncjones

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the cleanup of a Git worktree and Jira ticket after a pull request is merged, including branch removal, worktree deletion, and Jira ticket status update.

Core Features & Use Cases

  • PR Merged Branch and Worktree Cleanup: Ensures clean-up of the worktree associated with the merged PR, deleting the local and remote branches, and cleaning up any remaining worktree directories.
  • Jira Ticket Sync: Updates the linked Jira issue to the 'Done' status, assigns it to the current user, adds it to the current sprint, sets its epic, and posts a resolution comment.
  • Use Case: After a pull request is successfully merged, run this Skill to automatically clean up the temporary branch and worktree, and update the corresponding Jira issue.

Quick Start

Use the post-merge skill after a pull request has been merged to perform the post-merge cleanup.

Frequently Asked Questions about post-merge

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

FAQPage Schema
How do I clean up local branches and worktrees after a pull request merge?

Post-merge cleanup removes Git worktrees and local or remote branches following a pull request merge. This prevents obsolete development artifacts from accumulating in your local repository environment.

How do I automatically transition a Jira ticket to Done when a PR merges?

Automating Jira ticket sync transitions linked issues to Done, assigns them to the current user, updates sprints and epics, and posts resolution comments following a pull request merge.

Do I need GitHub Actions to automate Jira ticket updates and branch deletion?

Automating Jira ticket updates and Git branch deletion assumes usage of GitHub Actions. You also need access to your Jira cloud_id and jira_account_id to authenticate and manage ticket transitions properly.

What is the best way to sync Jira issues and delete Git branches after merging?

Running a post-merge cleanup process handles Git worktree deletion, local and remote branch removal, and Jira ticket synchronization simultaneously to streamline the pull request merge aftermath.

Can I update Jira sprints and epics automatically after a pull request is merged?

Post-merge automation updates linked Jira issues by adding them to the current sprint, setting their epic, assigning them to the user, and transitioning the ticket status to Done after a pull request merge.

Why does my post-merge branch cleanup fail to update Jira tickets?

Post-merge Jira ticket updates require valid cloud_id and jira_account_id credentials. If these identifiers are missing or incorrect, the automation cannot access the Jira issue tracking system to transition statuses or post comments.