finishing-a-development-branch

Present merge, pull request, or cleanup options after feature branch completion.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/min-zou/obsidian-doc --skill finishing-a-development-branch-min-zou
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/min-zou/obsidian-doc/tree/main/format/areas/system/agent-skills/cursor-personal/superpowers/skills/finishing-a-development-branch
Command: npx skills add https://github.com/min-zou/obsidian-doc --skill finishing-a-development-branch-min-zou

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ensures the completion of development work by providing structured options for merging, creating pull requests, or cleaning up branches.

Core Features & Use Cases

  • Merge Management: Provides a systematic approach to merging completed feature branches into a base branch.
  • Pull Request Creation: Streamlines the process of pushing code to a remote repository and creating a pull request.
  • Branch Cleanup: Offers options for keeping branches, pushing them as pull requests, or discarding them entirely.

Quick Start

Run the finishing-a-development-branch skill to automatically verify tests, determine the base branch, and choose the action you'd like to take with the 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 a development branch merge into a base branch?▼

To merge a development branch, the process verifies that tests pass and identifies the base branch. It then presents structured options to directly execute the merge operation into the base branch.

What is the best way to create a pull request after finishing a feature branch?▼

Creating a pull request after finishing a feature branch involves pushing code to a remote repository. The workflow streamlines this by determining the base branch and presenting a structured pull request creation option.

Can I discard a feature branch and clean it up after development?▼

Yes, you can discard and clean up a feature branch after development by selecting the cleanup option. This allows you to entirely discard the branch instead of keeping it or pushing it as a pull request.

Do I need to pass tests before managing branch cleanup or pull requests?▼

Yes, tests must be passed before you can manage branch cleanup or pull requests. The workflow requires testing to be passed and base branch determination before presenting any merge, pull request, or cleanup options.

How does branch management handle choosing between merging and creating a PR?▼

Branch management handles this by presenting structured options upon feature branch completion. After verifying tests and determining the base branch, you simply choose whether to execute a direct merge or create a pull request.