skills.rest
gwozai
gwozaiCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Guides users through verifying tests, merging, creating PRs, and cleaning up git branches.

Updated May 29, 2026
Search Tags:#git#development workflow#branch management#PR creation#merge options
One-click install
npx skills add https://github.com/gwozai/claude-code-practice --skill finishing-a-development-branch-gwozai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/gwozai/claude-code-practice/tree/main/github-repos/superpowers/skills/finishing-a-development-branch
Command: npx skills add https://github.com/gwozai/claude-code-practice --skill finishing-a-development-branch-gwozai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The finishing-a-development-branch Skill helps streamline the process of completing a development branch in a git repository, guiding users through merge, Pull Request, or cleanup options.

Core Features & Use Cases

  • Verify Tests: Before proceeding, the skill checks if all tests pass.
  • Detect Environment: Determines if the workspace is on a normal branch or a detached HEAD.
  • Present Options: Offers clear, structured options for merge, PR, keeping the branch as-is, or discarding it.
  • Execute Choice: Guides the user in merging locally, creating a PR, keeping the branch, or discarding it.
  • Cleanup Workspace: Cleans up the workspace as necessary after a merge or discard.

Quick Start

Run 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 finish a git development branch and choose between merging or creating a PR?▼

Finishing a git development branch involves verifying tests, detecting the environment, and selecting options to merge locally, create a Pull Request, keep the branch, or discard it entirely.

What is the best way to manage git branch cleanup after merging changes?▼

The best way to manage git branch cleanup after merging is to use a structured workflow that executes the merge and then automatically cleans up the workspace, ensuring no residual files or branch references remain.

Does this branch management workflow verify tests before allowing a git merge?▼

Yes, this branch management workflow explicitly checks if all tests pass before presenting any merge, PR, or discard options to ensure code quality before completion.

Can I create a Pull Request directly from a detached HEAD state in git?▼

When finishing a branch from a detached HEAD state, the workflow detects the environment and guides you through appropriate PR creation or merge options, though standard branch management typically requires a named branch reference.

What should I do if I want to keep my git development branch as-is instead of merging?▼

To keep your git development branch as-is instead of merging, select the 'keep branch' option during the workflow, which preserves your current workspace state without executing a local merge or cleanup.

Related Skills

Explore More Software Engineering Skills→
JiangAustinJiangAustin

finishing-a-development-branch

Verify test status and present merge, pull request, keep, or discard paths for git branches.

Community
Advanced
falconntfalconnt
3

finishing-branch

Finalize Git feature branches with test verification and structured merge options.

Community
Basic
Room-CRoom-C

rc:commit-pr

Stage changes, commit with conventional messages, push, and create pull requests via GitHub CLI.

Official
Advanced
alexandersumeralexandersumer
1

clear-merge-blockers

Identify and resolve merge blockers in code repositories with CI/CD integration.

Community
Advanced