08-wrap

To wrap up a git worktree after finishing a feature, you need to verify tests, review repository status, and coordinate cleanup actions. The wrap-up process supports local merge, pull request creation, branch retention, or deletion.

Documenting lessons learned before closing a development branch involves running a structured workflow to capture documentation updates, automation opportunities, duplicate validation, and follow-up tasks from your session.

Verifying your test suite passes before creating a pull request requires checking the repository state and confirming the relevant test suite succeeds before initiating any final cleanup or handoff actions.

Yes, you can retain a branch while cleaning up the worktree after a session. The wrap-up process supports branch retention or deletion alongside worktree cleanup based on your finalization needs.

Yes, the wrap-up workflow captures automation opportunities from your code changes. It uses a two-phase specialist agent process to extract documentation updates, duplicate checks, and follow-up work.

You should not use an automated wrap-up process for your pull request if your development session lacks completed work, failing tests, or the need for structured repository state coordination and handoff.