Automate post-merge PR confirmation, main updates, and worktree cleanup.
npx skills add https://github.com/danievanzyl/code-skills --skill wrap-up-danievanzyl
Please help me install this Agent Skill. Skill: wrap-up Source: https://github.com/danievanzyl/code-skills/tree/main/skills/wrap-up Command: npx skills add https://github.com/danievanzyl/code-skills --skill wrap-up-danievanzyl
The post-merge motion you do by hand every time a PR lands: confirm merged → update main → close worktree/branch → offer a handoff → say what's next. Orchestration glue — it leans on git-worktree (cleanup) and handoff (the doc), it does not reimplement them.
After a PR is merged, run wrap-up to close the worktree, update main, and optionally generate a handoff document.
High-intent search queries and answers about installing and using this skill.
Automating post-merge cleanup involves validating the PR state, updating the main branch, and removing local worktrees. This Skill orchestrates that flow by delegating the cleanup to git-worktree mechanisms after confirming a PR is merged.
Handling cross-repo handoffs requires coordinating cleanup and signaling sibling repositories for attention. This Skill orchestrates multi-repo workflows by delegating documentation generation to the handoff skill after refreshing main branches.
Yes, generating handoff documentation while closing a worktree is supported via argument parsing for an optional handoff topic. The Skill delegates this documentation task to the handoff skill during the post-merge workflow.
Multi-repo workflow automation for branch cleanup validates merged PRs across related repositories, refreshes main, and removes obsolete worktrees. It coordinates downstream messaging to indicate which sibling repos require further attention.
Yes, the git-worktree mechanism is required because this Skill acts as orchestration glue and delegates the actual worktree and branch removal to it rather than reimplementing those cleanup functions.
Using an orchestration Skill prevents manual errors by automating the end-to-end post-merge motion: confirming the merge, updating main, cleaning worktrees, and offering handoff documentation across multiple repositories seamlessly.
Clawdi-AIMerge GitHub pull requests via squash after validating checks and branch status.
dokdo2013Identify cross-repo side effects from code changes via grep-based symbol analysis.
coco-researchCreate isolated git workspaces with separate repos and planning directories.
whoabuddySwitch to the default branch, pull updates, and delete merged feature branches.
