finishing-a-development-branch

Guides completion of development branches through verified merge, pull request, or cleanup options.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Emmanuel-R8/aikos --skill finishing-a-development-branch-emmanuel-r8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Emmanuel-R8/aikos/tree/main/.cursor/skills/finishing-a-development-branch
Command: npx skills add https://github.com/Emmanuel-R8/aikos --skill finishing-a-development-branch-emmanuel-r8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementation work is done, developers often merge broken code, forget to clean up worktrees, or accidentally delete work. This Skill enforces a safe, structured completion workflow for Git development branches. ## Core Features & Use Cases - Test Gate Before Completion: Runs the project's test suite first and blocks any merge or PR if tests fail. - Four Structured Options: Presents exactly four choices—merge locally, push and create a PR, keep the branch as-is, or discard—then executes the chosen workflow with the correct Git commands. - Safe Cleanup and Discard Protection: Cleans up Git worktrees only when appropriate and requires typed confirmation before permanently deleting a branch. - Use Case: After finishing a feature branch in a Git worktree, invoke this Skill to verify tests pass, create a pull request via gh pr create, and remove the worktree in one guided flow. ## Quick Start Use the finishing-a-development-branch skill to complete my current feature branch now that all tests pass.

Frequently Asked Questions about finishing-a-development-branch

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

FAQPage Schema
How do I safely finish a Git feature branch after implementation?▼

Verify the test suite passes first, then choose between merging locally, pushing and creating a pull request, keeping the branch, or discarding it. Each option runs the appropriate git commands and handles worktree cleanup accordingly.

How to create a pull request from a feature branch using the GitHub CLI?▼

Push the branch with git push -u origin, then run gh pr create with a title and a body containing a summary and test plan. The Skill generates this PR automatically when you choose the push-and-PR option.

What happens if tests fail before merging a branch?▼

The workflow stops immediately and reports the number of failing tests. No merge, pull request, or cleanup proceeds until the failures are fixed and the test suite passes.

When should Git worktrees be removed after finishing a branch?▼

Worktrees are removed only after a local merge or a confirmed discard. When creating a pull request or keeping the branch as-is, the worktree is preserved so the work remains accessible.

Can I recover a branch after choosing the discard option?▼

No. Discard permanently deletes the branch and its commits using git branch -D, which is why the workflow requires typing 'discard' as explicit confirmation before executing.