finishing-a-development-branch

Verify tests and execute merge, Pull Request, or cleanup workflows.

3|2|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/Crumbgrabber/llm_system_template_agents_skills_patterns_tools_prompts --skill finishing-a-development-branch-crumbgrabber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Crumbgrabber/llm_system_template_agents_skills_patterns_tools_prompts/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/Crumbgrabber/llm_system_template_agents_skills_patterns_tools_prompts --skill finishing-a-development-branch-crumbgrabber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of concluding development work by providing clear, actionable options for integrating changes, ensuring a smooth transition from feature development to main codebase.

Core Features & Use Cases

  • Test Verification: Automatically checks if tests pass before proceeding.
  • Branch Integration Options: Offers clear choices for merging locally, creating a Pull Request, or deferring the integration.
  • Worktree Management: Handles the cleanup of development worktrees to maintain a tidy environment.
  • Use Case: After completing a new feature, use this skill to ensure all tests pass, then choose to merge the branch locally, create a PR for review, or keep the branch for later.

Quick Start

Use the finishing-a-development-branch skill to finalize your 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 and ensure tests pass before merging?

Finalizing a git development branch requires verifying that all tests pass before proceeding. The workflow automatically checks test status, then presents structured options to merge locally, create a Pull Request, or defer integration.

What is the best way to manage worktree cleanup after completing feature development?

Worktree cleanup after feature development is handled automatically during the branch integration process. When you select your preferred integration method, the workflow manages branch integration and worktree cleanup to maintain a tidy environment.

Can I choose between creating a pull request or merging locally when finishing a branch?

Yes, you can choose between merging locally, creating a Pull Request for code review, or deferring integration when finishing a branch. These structured options are presented after mandatory test verification succeeds.

Does branch integration require test verification before code integration?

Test verification is mandatory before any code integration occurs. The workflow ensures code quality by automatically checking if tests pass before presenting options for merge, Pull Request creation, or cleanup.

What should I do if I want to keep my development branch for later instead of merging?

Keeping your development branch for later is supported by deferring the integration. When presented with branch integration options after test verification, simply choose to defer integration and keep the branch active.

How does branch management handle the transition from feature development to the main codebase?

Branch management handles the transition by streamlining the conclusion of development work. It provides clear, actionable options for integrating changes, ensuring a smooth flow from feature development to the main codebase after tests pass.