What problem does it solve? After a pull request is merged, teams often forget follow-up chores: closing linked issues, updating the changelog, creating follow-up tickets, deleting stale branches, syncing develop, and marking working plans as completed. This Skill orchestrates that entire post-merge checklist so nothing falls through the cracks. ## Core Features & Use Cases - Ten-step post-merge workflow: Verifies merge status via GitHub CLI, identifies linked issues, drafts changelog entries, detects follow-up signals in PR bodies, and triggers EVAL backlog tickets when in-source canonical skill or prompt files change. - Delegation to sub-skills: Hands off branch deletion to mj-agent-git-delete, develop sync to mj-agent-git-sync, issue creation to mj-agent-git-issue, and follow-up worktree creation to mj-agent-git-branch, enforcing a worktree-per-PR model. - Plan lifecycle management: Locates the associated working plan and outputs a frontmatter diff draft (state active to completed) for the user to apply, keeping human-in-the-loop control. - Use Case: After merging PR #42 which closed issue #38, run this Skill to get a complete checklist: issue closure confirmation, a changelog draft, a follow-up issue draft, branch cleanup commands, and a plan state update diff. ## Quick Start Tell the assistant that PR number 42 was just merged and ask it to run the post-merge cleanup checklist.
