post-merge-cleanup

Automate local post-merge cleanup and issue tracker updates.

9|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/lhpaul/ai-dev-framework-template --skill post-merge-cleanup-lhpaul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-merge-cleanup
Source: https://github.com/lhpaul/ai-dev-framework-template/tree/main/.codex/skills/post-merge-cleanup
Command: npx skills add https://github.com/lhpaul/ai-dev-framework-template --skill post-merge-cleanup-lhpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a development PR is merged and the remote branch deleted, this Skill cleans up the local repository by syncing with origin, switching to develop, pulling, deleting the local branch, and updating the related issue tracker.

Core Features & Use Cases

  • Automates local post-merge cleanup including origin sync, branch deletion, and develop branch maintenance.
  • Updates the related issue tracker using the branch name to infer IDs and status transitions across supported trackers (e.g., Linear, GitHub Projects, and other trackers).
  • Integrates with a centralized workflow protocol to guide post-merge actions while preserving safe guardrails.

Quick Start

Run the post-merge cleanup script from the repository root using the merged branch name as an argument.

Frequently Asked Questions about post-merge-cleanup

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

FAQPage Schema
How do I automate local git branch cleanup after a PR merge?

Git branch cleanup after a PR merge is automated by running a shell script that syncs with origin, switches to develop, pulls, deletes the local branch, and updates the issue tracker. Pass the merged branch name as an argument from the repository root.

What's the best way to sync local branches and update issue trackers after merging?

Syncing local branches and updating trackers after merging is handled by a centralized workflow protocol script that infers issue IDs from the branch name. It transitions issue statuses across supported trackers like Linear and GitHub Projects while preserving safe guardrails.

Does post-merge cleanup work with multiple issue trackers like Linear and GitHub Projects?

Post-merge cleanup supports multiple issue trackers including Linear and GitHub Projects via configured protocols. The script uses the branch name to infer tracker IDs and applies appropriate status transitions across all supported platforms.

How to delete local git branches and pull develop after a remote merge?

Deleting local branches and pulling develop after a remote merge requires running scripts/development-workflow/post-merge-cleanup.sh from the repository root. The script syncs with origin, switches to develop, pulls latest changes, and prunes the merged local branch.

Do I need a specific script to run post-merge repository cleanup?

Post-merge repository cleanup requires the post-merge cleanup script located at scripts/development-workflow/post-merge-cleanup.sh in your repository. Run it from the repository root using the merged branch name as an argument to execute all cleanup steps.