finishing-a-development-branch

Validate tests and TDD compliance before presenting merge, PR, keep, or discard options.

4|1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/samjhecht/wrangler --skill finishing-a-development-branch-samjhecht
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/samjhecht/wrangler/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/samjhecht/wrangler --skill finishing-a-development-branch-samjhecht

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

Integrating completed development work back into the main codebase can be error-prone without proper verification and a clear decision-making process for merging or creating pull requests.

Core Features & Use Cases

  • Test Verification: Mandates running the full test suite and confirming all tests pass before presenting any integration options.
  • Structured Options: Presents exactly four clear options: merge locally, push and create a Pull Request, keep the branch, or discard the work.
  • Safe Cleanup: Handles the cleanup of Git worktrees and branches based on the chosen option, preventing lingering development environments.
  • Use Case: When your implementation is complete, all tests pass, and you need to decide how to integrate your work into the main branch or prepare it for review and cleanup.

Quick Start

My feature branch 'feature/new-dashboard' is complete and all tests pass. Guide me through finishing this development branch.

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 merge a development branch safely after tests pass?

Merging a development branch safely requires verifying all tests pass, confirming code review completion, and validating TDD compliance before integration. This Skill automates those checks and presents merge, pull request, or discard options based on your workflow.

What should I verify before merging my feature branch into main?

Before merging, verify the full test suite passes, code review requirements are met, and TDD practices are followed. This Skill validates all three and guides you through safe merge or pull request creation with cleanup of Git worktrees.

Can I create a pull request and clean up my branch automatically?

Yes. This Skill automates the pull request creation workflow using gh, then handles safe cleanup of Git worktrees and branches based on whether you merge locally, push for review, keep the branch, or discard the work.

What happens if tests fail on my development branch?

If tests fail, this Skill halts the merge decision process and requires you to fix failing tests before proceeding. It mandates a passing test suite as a prerequisite to any integration option.

How do I decide between merging locally versus creating a pull request?

This Skill presents four structured options after validation: merge locally for immediate integration, push and create a pull request for team review, keep the branch for later decisions, or discard completed work. Your workflow determines which option suits your needs.

Does this work with repositories using Git worktrees?

Yes. This Skill handles safe cleanup of Git worktrees alongside branch cleanup, preventing lingering development environments regardless of whether you use standard branches or worktree-based workflows.