skills.rest
zhou533
zhou533COMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Verify test execution and manage Git merge, pull request, or branch cleanup.

Updated Mar 3, 2026
Search Tags:#git#testing#development workflow#pull request#branch management#code integration
One-click install
npx skills add https://github.com/zhou533/UnVault --skill finishing-a-development-branch-zhou533
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/zhou533/UnVault/tree/main/.claude/skills/finishing-a-development-branch
Command: npx skills add https://github.com/zhou533/UnVault --skill finishing-a-development-branch-zhou533

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of finalizing development work by providing clear, structured options for integrating changes and ensuring code quality before merging or deploying.

Core Features & Use Cases

  • Test Verification: Automatically runs the project's test suite to ensure code stability.
  • Branch Integration Guidance: Offers clear choices for merging, creating pull requests, or managing the branch.
  • Worktree Management: Handles the cleanup or preservation of development worktrees based on the chosen workflow.
  • Use Case: After completing a new feature, use this Skill to verify all tests pass, then choose to either merge the branch locally, create a pull request, keep the branch for later, or discard the work entirely, with appropriate cleanup actions taken.

Quick Start

Use the finishing-a-development-branch skill to complete the current development work.

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 finalize a git development branch after completing a feature?▼

Finalizing a git development branch involves verifying test execution and selecting a structured integration path like merging, creating a pull request, or discarding work, followed by worktree cleanup.

What is the best way to manage git branch integration and code quality checks?▼

Managing git branch integration requires running the project's test suite to ensure code stability before presenting clear options for merging or creating a pull request into the main codebase.

Can I create a pull request after verifying tests on my development branch?▼

Yes, creating a pull request after verifying tests on your development branch is a supported option, presented alongside merging or discarding work to ensure controlled code integration.

How do I clean up a git worktree after merging my branch?▼

Cleaning up a git worktree after merging your branch is handled automatically based on your chosen workflow, preserving or removing the development worktree to maintain a controlled environment.

When should I discard work on a development branch instead of merging?▼

You should discard work on a development branch instead of merging when tests fail or the feature is no longer needed, allowing you to entirely remove the changes and clean up the worktree.

Related Skills

Explore More Software Engineering Skills→
samueriosamuerio

agent-workspace

Create isolated branch-scoped workspaces using git worktree and tmux.

Community
Advanced
oxieoxie

staging-deployment-phase

Automate staging deployment with auto-merge for merged pull requests.

Community
Intermediate
spencerbeggsspencerbeggs

review

Triage GitHub pull request review comments and apply code fixes.

Community
Advanced
UniClipboardUniClipboard
1.5k

finishing-a-development-branch

Offer merge, PR, keep, or discard options after tests pass.

Official
Advanced