finishing-a-development-branch

Verify tests and present integration options for completing a Git branch.

134|27|Updated Nov 16, 2025

Search Tags:#git #testing #development workflow #pull request #branch management #code integration

Ready to run

npx skills add https://github.com/projectbluefin/dakota --skill finishing-a-development-branch-projectbluefin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/projectbluefin/dakota/tree/main/.opencode/skills/finishing-a-development-branch
Command: npx skills add https://github.com/projectbluefin/dakota --skill finishing-a-development-branch-projectbluefin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of concluding development work on a branch, ensuring code quality and providing clear, structured options for integration or cleanup.

Core Features & Use Cases

Test Verification: Automatically runs project tests to ensure code stability before integration.
Integration Options: Presents clear choices for merging locally, creating a Pull Request, or discarding work.
Worktree Management: Handles the cleanup or preservation of development worktrees based on the chosen integration path.
Use Case: After finishing a new feature, you can use this skill to automatically run tests, check for related epics, and then choose to either merge the branch locally, push it for a PR, or discard it if the work is no longer needed, ensuring a clean repository state.

Quick Start

Use the finishing-a-development-branch skill to finalize your current feature 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 finish a Git development branch and verify tests before integration?▼

To finish a Git development branch, you can run project tests to verify code stability, determine the base branch, and then choose to merge locally, create a pull request, or discard the work.

What is the best way to manage branch cleanup and worktree preservation after merging?▼

The best way to manage worktree cleanup is to select an integration path that automatically handles the preservation or removal of development worktrees based on whether you merge locally or discard the work.

Can I discard a Git branch and remove its worktree if the development work is no longer needed?▼

Yes, you can discard development work on a Git branch, which removes the unnecessary changes and handles the associated worktree cleanup to ensure a clean repository state.

Does finishing a development branch support creating a pull request and tracking related epics?▼

Yes, finishing a development branch supports creating a pull request for code integration and includes optional epic tracking to check for related epics during the workflow.

When should I choose a local merge over a pull request for my Git branch?▼

You should choose a local merge when you want to integrate development work directly into the base branch without remote code review, preserving or cleaning the worktree locally afterward.