skills.rest
dsifry
dsifryCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

finishing-a-development-branch

Evaluate test results and offer merge, PR, keep, or discard options.

60|4|Updated Jan 15, 2026
Search Tags:#git#workflow#merge#branch-management#pull-request#tests#finishing
One-click install
npx skills add https://github.com/dsifry/goodtogo --skill finishing-a-development-branch-dsifry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/dsifry/goodtogo/tree/main/.claude/plugins/superpowers/skills/finishing-a-development-branch
Command: npx skills add https://github.com/dsifry/goodtogo --skill finishing-a-development-branch-dsifry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams finish development work by evaluating readiness and guiding the final integration path. It ensures a clean handoff by presenting deterministic options for merging, creating a PR, keeping the branch for later work, or discarding the changes.

Core Features & Use Cases

  • Option-driven closing: presents four explicit, minimal actions (merge locally, push and create PR, keep as-is, or discard) after tests pass.
  • Safety-first workflow: verifies test results before offering options and suggests cleanup steps when appropriate.
  • Use Case: after implementing a feature and passing all tests, run this skill to choose the final integration path and optionally clean up the feature branch.

Quick Start

Announce usage and start with tests, base branch, and chosen option.

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 feature branch after tests pass?▼

This skill guides finishing a git feature branch by verifying test results and offering four explicit merge or cleanup options: merge locally, push and create a pull request, keep the branch, or discard the work.

What is the best way to guide a pull request workflow for feature branch management?▼

Guiding a pull request workflow requires a safety-first process that verifies passing tests before presenting deterministic options for pushing and creating a PR, merging locally, keeping, or discarding the branch.

Can I discard local git changes and clean up the branch after a failed feature attempt?▼

Yes, you can discard local git changes and clean up the branch by selecting the explicit discard option provided after the skill evaluates your branch readiness and test results.

Does this branch finishing workflow detect the base branch automatically?▼

Yes, the branch finishing workflow includes base-branch detection to determine the correct target for merging or creating a pull request as part of its guided cleanup and integration options.

When should I keep a git feature branch instead of merging or creating a pull request?▼

You should keep a git feature branch instead of merging when the work is not ready for final integration, utilizing the explicit keep-as-is option to pause development and skip optional cleanup steps.

Related Skills

Explore More Software Engineering Skills→
Moonsong-LabsMoonsong-Labs
3

finishing-a-development-branch

Verify tests and merge, push, preserve, or discard a feature branch.

Official
Advanced
minfengyuanminfengyuan
1

finishing-a-development-branch

Verify tests, then merge, push, preserve, or discard a feature branch.

Community
Intermediate
edwifiguyedwifiguy
1

git-workflow

Enforce best practices for commits, branches, merges, and pull requests.

Community
Intermediate
miles990miles990

finishing-a-development-branch

Present four merge, PR, keep, or discard options after tests pass.

Community
Intermediate