finishing-a-development-branch

Verify tests and complete git feature branches via merge, PR, or discard.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/PlazaCC/antes-da-tela --skill finishing-a-development-branch-plazacc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/PlazaCC/antes-da-tela/tree/main/.agents/skills/finishing-a-development-branch
Command: npx skills add https://github.com/PlazaCC/antes-da-tela --skill finishing-a-development-branch-plazacc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many feature branches finish development without a clear, safe path to integrate or dispose of work; this Skill removes ambiguity by verifying tests, offering explicit choices, and enforcing safe cleanup and confirmation rules so work is not lost or merged unsafely.

Core Features & Use Cases

  • Test Verification: Require and verify passing test suites before any merge, push, or PR creation.
  • Structured Decision Flow: Determine the correct base branch, then present exactly four concise options: merge locally, push and create a PR, keep the branch, or discard the work.
  • Safe Execution & Cleanup: Execute merges, push branches and create PRs with a defined message format, require typed confirmation for destructive discards, and remove git worktrees when appropriate.
  • Use Case: After completing a feature and running tests locally, use this Skill to decide whether to merge into main, open a PR for review, preserve the worktree for further edits, or securely discard the branch with confirmation.

Quick Start

Use the finishing-a-development-branch skill to verify tests, choose an integration option, and perform the selected merge, PR creation, or safe cleanup.

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 safely merge a git feature branch after running tests?▼

To safely merge a git feature branch, verify passing tests first, determine the appropriate base branch, then choose to merge locally or push and create a pull request with a defined message format.

What is the best way to clean up git worktrees after finishing a branch?▼

The best way to clean up git worktrees is to use a structured workflow that removes worktrees when appropriate after you merge, create a pull request, keep, or discard the development branch.

Can I securely discard an abandoned git branch without losing work?▼

You can securely discard an abandoned git branch by selecting the discard workflow option, which requires typed confirmation for destructive actions to prevent accidental data loss.

Do I need to verify tests before creating a pull request from a feature branch?▼

Yes, test verification is required before creating a pull request, pushing, or merging a feature branch to ensure work is not merged unsafely and prevents integration failures.

What should I do if I want to keep a development branch instead of merging it?▼

If you want to keep a development branch, select the explicit option to preserve the branch and its worktree for further edits instead of merging, creating a pull request, or discarding.