finishing-a-development-branch

Automates finishing development branches with test verification, merge/PR options, and cleanup.

53|4|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/roundpilot/superpowers-antigravity --skill finishing-a-development-branch-roundpilot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/roundpilot/superpowers-antigravity/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/roundpilot/superpowers-antigravity --skill finishing-a-development-branch-roundpilot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of finishing a development branch by guiding the user through merge, PR, or cleanup options, ensuring code integrity and workflow completion.

Core Features & Use Cases

  • Test Verification: Ensures all tests pass before presenting merge or PR options.
  • Environment Detection: Identifies the workspace state and selects the appropriate workflow.
  • Merge and PR Options: Provides structured options for merging locally, pushing and creating a PR, keeping the branch, or discarding the work.
  • Cleanup Workspace: Cleans up worktrees based on the user's chosen action.

Quick Start

Activate the finishing-a-development-branch skill to complete your 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 automate finishing a development branch with merge and pull request options?

Test verification ensures all tests pass before presenting merge or pull request options. This check guarantees code integrity and workflow completion before you proceed with branch merging or cleanup actions.

What options are available when completing a development branch merge?

When completing a development branch, you can choose between merging locally, pushing to create a pull request, keeping the branch active, or discarding the work entirely. The workspace is then cleaned up based on your chosen action.

Can I use branch completion automation for both local and external workflows?

If you encounter workflow errors during development branch completion, the automation provides detailed error handling to guide you. It detects the workspace state and supports worktree cleanup based on your chosen merge or pull request action.

What is the best way to handle branch cleanup after a pull request?

The best way to handle branch cleanup is using automation that cleans up worktrees based on your chosen action. After test verification and pull request creation, it ensures the workspace is properly maintained without leaving residual branches.