finishing-a-development-branch

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

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/AarushiShah/coding-agents-databricks-apps --skill finishing-a-development-branch-aarushishah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/AarushiShah/coding-agents-databricks-apps/tree/main/.claude/skills/finishing-a-development-branch
Command: npx skills add https://github.com/AarushiShah/coding-agents-databricks-apps --skill finishing-a-development-branch-aarushishah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementation work is done, developers often merge broken code, forget to run tests, or leave stale branches and worktrees behind. This Skill enforces a disciplined finish: verify tests pass, then choose exactly one of four structured completion paths. ## 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 merge locally, push and create a PR via gh pr create, keep the branch as-is, or discard with typed confirmation. - Worktree Cleanup: Automatically removes git worktrees for merge and discard paths while preserving them when the branch is kept. - Use Case: After finishing a feature branch in a git worktree, invoke this Skill to verify tests, create a pull request with a summary and test plan, and clean up 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 finish a git feature branch after implementation is complete?

First run the project's test suite to confirm everything passes, then choose one of four options: merge locally into the base branch, push and create a pull request, keep the branch as-is, or discard it. Never merge with failing tests.

How to create a GitHub pull request from a feature branch?

Push the branch with git push -u origin, then run gh pr create with a title and body containing a summary of changes and a test plan checklist. Verify tests pass on the branch before creating the PR.

When should I remove a git worktree after merging?

Remove the worktree only after merging locally or discarding the branch, using git worktree remove. Keep the worktree when you create a pull request or keep the branch as-is, since the work may still be needed.

What happens if tests fail before merging a branch?

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

How do I safely delete a git branch without losing work?

Require explicit typed confirmation such as 'discard' before deletion, showing the branch name, commit list, and worktree path first. Then use git branch -D only after confirmation is received.