Finishing a Development Branch

What it does

Provides an end-to-end playbook for wrapping up a development branch: sanity checks, pre-push verification (lint/type/test/build), diff self-review, selecting integration strategy (PR, merge, squash, rebase), composing PR/merge messages, pushing/creating PRs, and cleanup/recovery steps. Includes templates, checklists, and recommended commands.

When to use it

Use when implementation is complete and the branch is ready to be merged or landed — e.g., before opening a PR, when deciding between rebase vs squash, when cleaning up worktrees, or when recovering from a misstep like an accidental force-push.

What's included

• Scripts: none detected (has_scripts=false).
• References: contains a references/ folder with pre-push checks, integration strategies, PR templates, cleanup and recovery guides.
• Instructions: detailed phase-by-phase guidance (Working-tree sanity, Pre-push verification, Diff review, Integration selection, Message writing, Push & PR creation, Cleanup, Recovery) plus critical rules and quality checklist.

Compatible agents

Designed for agents that interface with git and CLI helpers (Cursor, Claude Code, Copilot-style assistants) and that can call out to gh/git in host environments or provide guidance to developers.