skills.rest
the-agency-ai
the-agency-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr-captain-post-merge

Automates GitHub post-merge validation, release tagging, and branch cleanup workflows.

39|6|Updated Jan 5, 2026
Search Tags:#automation#git#ci/cd#worktrees#github#release
One-click install
npx skills add https://github.com/the-agency-ai/the-agency --skill pr-captain-post-merge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-captain-post-merge
Source: https://github.com/the-agency-ai/the-agency/tree/main/.claude/skills/pr-captain-post-merge
Command: npx skills add https://github.com/the-agency-ai/the-agency --skill pr-captain-post-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It streamlines the post-merge process by verifying that a pull request has been correctly merged, synchronizing code across worktrees, creating releases, and cleaning up branches automatically.

Core Features & Use Cases

  • Merge verification and synchronization: Confirms that the merge commit is in place and propagates updates to all worktrees.
  • Automated release creation: Ensures every merge results in a GitHub release following versioning protocols.
  • Branch cleanup and reporting: Deletes merged PR branches and provides a comprehensive post-merge report, reducing manual effort and error.

Quick Start

Run /pr-captain-post-merge <pr-number> after a PR has merged to verify, release, and clean up automatically.

Frequently Asked Questions about pr-captain-post-merge

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

FAQPage Schema
How do I automate GitHub post-merge verification and branch cleanup?▼

Automating GitHub post-merge verification involves confirming the merge commit, synchronizing updates across worktrees, and deleting merged branches. This ensures release consistency and reduces manual cleanup effort.

What is the best way to automate release creation after a PR merges?▼

Automated release creation after a PR merge ensures every merged pull request results in a GitHub release following versioning protocols. It automatically detects merge status and tags the release without manual intervention.

How does post-merge synchronization work with multiple git worktrees?▼

Post-merge synchronization with git worktrees propagates the verified merge commit updates to all active worktrees. This ensures all local development environments remain consistent with the newly merged base branch.

Can I run post-merge validation in my existing CI/CD pipelines?▼

Yes, post-merge validation fits directly into GitHub flow CI/CD pipelines. It detects the pull request merge status, creates the release, and cleans up branches automatically within your existing automation workflow.

Why do I need to delete branches after a pull request merges?▼

Deleting branches after a pull request merges prevents branch clutter and reduces manual errors. Automated branch cleanup removes the merged PR branches once verification and release tagging are successfully completed.

Related Skills

Explore More Software Engineering Skills→
alexandersumeralexandersumer
1

clear-merge-blockers

Identify and resolve merge blockers in code repositories with CI/CD integration.

Community
Advanced
aberrantCodeaberrantCode
1

git-cleanup

Audit and remove stale git worktrees and branches merged into dev.

Community
Advanced
bildzeitungbildzeitung
1

release

Propose, confirm, and execute software releases with SemVer and GitHub tagging.

Community
Advanced
pkuppenspkuppens

maintenance-cleanup

Clean up merged branches, worktrees, GitHub Actions runs, and tmp directories.

Community
Intermediate