skills.rest
Itzalive
ItzaliveCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

finishing-a-development-branch

Execute a structured merge or PR workflow after tests pass.

Updated Apr 15, 2026
Search Tags:#development#merge#branch-management#git-workflow#pull-request#finish
One-click install
npx skills add https://github.com/Itzalive/resistance-ai --skill finishing-a-development-branch-itzalive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Itzalive/resistance-ai/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/Itzalive/resistance-ai --skill finishing-a-development-branch-itzalive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams finalize development work by providing a structured, deterministic path to close a feature branch through a choice of merge, PR, cleanup, or discard after tests pass.

Core Features & Use Cases

  • Verify tests pass before proposing actions.
  • Offer four explicit end-to-end options: merge locally, push and create a PR, keep the branch for later, or discard the work.
  • Handle base-branch detection and optional worktree cleanup to maintain a clean repository state.

Quick Start

Use this skill to decide how to finish your feature work after tests pass and apply the chosen workflow.

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

To finalize a feature branch after tests pass, you select a structured workflow that detects the base branch and prompts you to merge locally, push a pull request, keep the branch, or discard the work.

What is the best way to manage branch cleanup and merge decisions in a collaborative project?▼

The best way to manage branch cleanup and merge decisions is applying a deterministic workflow that verifies tests, detects the base branch, and offers explicit options to merge, create a PR, keep, or discard.

Can I push a pull request directly from my local development branch?▼

Yes, you can push a pull request from your local development branch by selecting the PR creation option in the structured workflow, which handles the push operation and initiates the pull request process.

Do I need to verify tests before executing a git merge workflow?▼

Yes, you need to verify tests pass before executing a git merge workflow, as the structured completion process checks test verification before proposing any merge, PR, or discard actions.

When should I discard my development work instead of merging?▼

You should discard development work instead of merging when the feature is no longer needed or tests fail irrecoverably, using the discard option to clean the branch and maintain a tidy repository state.

Related Skills

Explore More Software Engineering Skills→
julianromlijulianromli
141

finishing-a-development-branch

Verify tests pass, determine the base branch, and present four completion options.

Community
Advanced
Kingdaddy007Kingdaddy007
2

DEVOPS & INFRASTRUCTURE

Govern infrastructure provisioning, CI/CD pipelines, monitoring, and disaster recovery.

Community
Advanced
bostonaholicbostonaholic
8

worktree-isolation

Create and remove isolated git worktrees for parallel development.

Community
Advanced
raas-devraas-dev
19

finishing-a-development-branch

Verify tests and present merge, PR, keep, or discard options for Git branches.

Official
Intermediate