finishing-a-development-branch

Verify tests and present merge, pull request, or branch preservation options.

5|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/treygoff24/autonomous-dev-kit --skill finishing-a-development-branch-treygoff24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/treygoff24/autonomous-dev-kit/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/treygoff24/autonomous-dev-kit --skill finishing-a-development-branch-treygoff24

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the final stages of a development task, ensuring code quality and providing clear options for integrating completed work into the main codebase.

Core Features & Use Cases

  • Test Verification: Automatically runs project tests to ensure code stability before integration.
  • Branch Integration Options: Offers clear choices for merging, creating pull requests, or preserving the branch.
  • 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, then choose to merge the feature into main, create a pull request for review, or simply keep the branch for later.

Quick Start

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

Finalizing a development branch involves automatically running project tests to verify code stability, then presenting structured options to merge, create a pull request, or preserve the branch. Tests must pass before integration proceeds.

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

Worktree cleanup is managed automatically based on your chosen integration path. When you select to merge, create a pull request, or preserve the branch, the workflow handles the corresponding cleanup or preservation of the development worktree.

Can I choose to preserve a branch instead of merging it into the main codebase?

Yes, branch preservation is a supported integration option. When finalizing development work, you can choose to keep the branch for later instead of immediately merging it or creating a pull request.

How does test verification work during the development workflow integration process?

Test verification runs project tests automatically to ensure code stability before allowing integration. This quality gate mechanism prevents untested or broken code from being merged, creating a pull request, or advancing in the development workflow.

Do I need to manually determine the base branch when creating a pull request?

No, the base branch is determined automatically during the finalization process. After verifying tests, the workflow identifies the correct base branch and presents structured options for integration, including pull request creation.