Post-Merge

Verify merged pull requests, merge origin updates, and create GitHub releases.

39|6|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/the-agency-ai/the-agency --skill post-merge-the-agency-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Post-Merge
Source: https://github.com/the-agency-ai/the-agency/tree/main/.claude/skills/post-merge
Command: npx skills add https://github.com/the-agency-ai/the-agency --skill post-merge-the-agency-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It automates the post-merge process by verifying PR merges, merging updates from origin, and triggering synchronization across worktrees, streamlining the GitHub collaboration workflow.

Core Features & Use Cases

  • PR Verification: Checks that a pull request has been properly merged into main, ensuring integrity before proceeding.
  • Automated Merging: Merges the latest changes from origin/master into the local branch, handling divergence and conflicts with safety checks.
  • Triggering Synchronization: Calls /sync-all to update all related worktrees, maintaining consistency across environments.
  • Release Automation: Creates a GitHub release tagged with the version derived from the PR, updating project versioning and ensuring release traceability.
  • Branch Cleanup: Deletes the PR branch locally after successful merge to maintain repository hygiene.
  • Reporting: Outputs a comprehensive status summary for tracking post-merge operations.

Quick Start

When a pull request is merged on GitHub, run this skill to verify the merge, update your local branches, create a new release, and clean up branches automatically.

Frequently Asked Questions about Post-Merge

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

FAQPage Schema
How do I automate GitHub pull request merge verification and local branch updates?

Automating GitHub pull request merge verification involves checking that a PR is merged into main, pulling origin changes, and synchronizing worktrees. This process ensures local repository integrity and continuous deployment readiness.

What is the best way to automate release tagging and branch cleanup after a Git merge?

Automating release tagging and branch cleanup after a Git merge requires creating a GitHub release tagged with the PR version, updating project versioning, and deleting the merged PR branch locally. This maintains repository hygiene and release traceability.

How does post-merge synchronization across Git worktrees work?

Post-merge synchronization across Git workworks works by triggering a synchronization command to update all related worktrees after merging origin changes. This maintains consistency across multiple local development environments.

Do I need to manually resolve conflicts when merging origin changes into my local branch?

You do not need to manually resolve conflicts in most cases because the merge process includes safety checks for divergence. However, mandatory release creation and conflict resolution checks are enforced before proceeding to ensure branch integrity.

Can I use this workflow to trigger continuous deployment after a GitHub PR is merged?

You can use this workflow to trigger continuous deployment after a GitHub PR is merged by verifying the merge, automating release creation, and synchronizing branches. It ensures safety through divergence checks before proceeding with deployment.