finishing-a-development-branch

Finishing a development branch involves a structured process that guides you through options for merging into a base branch, creating a Pull Request, or cleaning up. It automates test verification, context updates, and worktree management.

Automating worktree cleanup after merging a feature branch is handled by selecting a completion option that manages the worktree based on your choice to keep or discard it. This removes obsolete working directories automatically.

Yes, you need a repository with a test suite to create a Pull Request using this workflow. The process automates test verification before pushing your branch and generating the Pull Request with the appropriate information.

You can update project context and AGENTS.md files automatically when completing a branch by invoking a required librarian skill. This ensures your project documentation stays synchronized with the latest development changes.

Branch management workflow supports discarding a feature branch permanently through its cleanup options. You can choose to keep the branch as-is or discard it entirely, which also handles the associated worktree removal.

Limitations include a strict dependency on a librarian skill for context updates and requiring repository access with a valid test suite. Without these environmental prerequisites, the automated merge, Pull Request, and cleanup guidance cannot execute successfully.