wrap

Verify unresolved reviews, squash-merge pull requests, and clean up local worktrees.

3|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/auerbachb/claude-code-config --skill wrap-auerbachb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap
Source: https://github.com/auerbachb/claude-code-config/tree/main/.claude/skills/wrap
Command: npx skills add https://github.com/auerbachb/claude-code-config --skill wrap-auerbachb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wraps up an active pull request session by automating final verification, safe merge, follow-up issue creation, lesson capture, work-log synchronization, and local worktree cleanup so engineers don't leave dangling branches, unresolved findings, or orphaned worktrees.

Core Features & Use Cases

  • Pre-merge verification that checks for unresolved reviewer findings across review/comment endpoints and halts on blockers.
  • Authoritative merge-gate verification, acceptance-criteria checkbox parsing/ticking, and a safe squash-merge workflow that preserves CI and rebase safety.
  • Follow-up detection with deduplication and HHG two-ticket overrides, automated issue creation, and work-log entries.
  • Depth-adaptive lessons capture with memory deduplication and explicit worktree removal followed by branch cleanup.
  • Use case: an engineer finishing a feature branch in a multi-worktree setup can run this to verify ACs, merge, create follow-ups, record lessons, sync logs to the root repo, and remove the local worktree in one autonomous run.

Quick Start

Invoke the wrap skill to verify the PR, run the merge gate, squash-merge, create deduplicated follow-ups, record lessons, sync the work-log, and remove the worktree.

Frequently Asked Questions about wrap

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

FAQPage Schema
How do I automate pull request finalization and worktree cleanup in GitHub?

Automate pull request finalization by verifying unresolved review findings, performing a safe squash merge, creating deduplicated follow-up issues, syncing work-logs, and removing local worktrees in one autonomous run.

What is the safest way to squash merge a GitHub PR while preserving CI and rebase safety?

Safe squash merge involves running authoritative merge-gate verification, parsing and ticking acceptance-criteria checkboxes, and executing a squash-merge workflow that halts on unresolved blockers or failing CI checks.

How do I prevent duplicate follow-up issues when wrapping up a pull request?

Prevent duplicate follow-up issues by using deduplication detection with HHG two-ticket overrides during automated issue creation, ensuring only unique follow-ups are generated from unresolved review findings.

Do I need GitHub CLI to automate PR verification and worktree removal?

Yes, GitHub CLI access and local helper scripts are required to inspect review endpoints, run merge-gate checks, parse acceptance criteria, create issues, update session logs, and safely remove worktrees.

Why does my multi-worktree setup leave orphaned branches after a squash merge?

Orphaned branches and dangling worktrees occur when local cleanup is skipped; explicit worktree removal followed by branch cleanup ensures no dangling references remain after a squash merge.

Can I automate acceptance criteria verification before merging a GitHub pull request?

Acceptance criteria verification is automated by parsing AC checkboxes, running merge-gate checks against CI results, and halting the squash-merge workflow if any blockers or unresolved review findings remain.