finishing-a-development-branch

Validate test results and guide branch merge, pull request, retention, or discard workflows.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/fartmonarch/RenderMind --skill finishing-a-development-branch-fartmonarch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/fartmonarch/RenderMind/tree/main/.claude/skills/finishing-a-development-branch
Command: npx skills add https://github.com/fartmonarch/RenderMind --skill finishing-a-development-branch-fartmonarch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you safely finish implementation work once the code is done, the tests are passing, and you need to decide how to integrate or clean up the branch.

Core Features & Use Cases

  • Validation First: Confirms test results before any merge or PR step is offered.
  • Git-Aware Workflow Routing: Detects whether you are in a normal repository, a named worktree, or a detached HEAD and adapts the available options.
  • Safe Completion Choices: Guides you through local merge, pull request creation, keeping the branch, or discarding the work with confirmation.
  • Worktree Cleanup: Removes only the worktrees it is appropriate to clean up after merge or discard actions.
  • Use Case: After a feature branch passes tests, use this Skill to choose between merging it into main, opening a PR, preserving the branch for later, or discarding it safely.

Quick Start

Use the finishing-a-development-branch skill to check test status, inspect the git workspace, and guide me through the safest way to merge, open a PR, keep, or discard this completed 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 safely merge a finished git branch after tests pass?

To safely merge a finished git branch, you must verify test results, inspect the git environment, detect the base branch, and receive explicit confirmation before executing the local merge or branch cleanup.

What is the best way to clean up a git worktree after merging a feature branch?

The best way to clean up a git worktree after merging is to use a workflow that detects named worktrees and removes only the appropriate worktrees after confirming the merge or discard actions.

Can I discard changes on a detached HEAD without losing uncommitted work?

You can discard changes on a detached HEAD safely by using a workflow that detects the detached HEAD state, guides the discard process, and requires explicit confirmation before any destructive actions occur.

Does finishing a development branch require test verification before opening a pull request?

Yes, finishing a development branch requires test verification before opening a pull request, ensuring the workspace is validated and tasks pass before the final integration decision is guided.

How do I keep a development branch instead of merging it into the main branch?

To keep a development branch instead of merging, select the branch retention option during the workflow, which preserves the completed branch for later without executing destructive cleanup actions.