skills.rest
SESELOVSKYDarian
SESELOVSKYDarianCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

finishing-a-development-branch

Guides branch completion by verifying tests and executing merge, PR, keep, or discard options.

Updated Mar 31, 2026
Search Tags:#git#workflow#testing#pull request#worktree#merge#branch
One-click install
npx skills add https://github.com/SESELOVSKYDarian/Vase --skill finishing-a-development-branch-seselovskydarian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/SESELOVSKYDarian/Vase/tree/main/.agents/skills/finishing-a-development-branch
Command: npx skills add https://github.com/SESELOVSKYDarian/Vase --skill finishing-a-development-branch-seselovskydarian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementation work is done, developers often merge broken code, forget to clean up worktrees, or accidentally delete work. This Skill enforces a safe, structured completion workflow for development branches. ## Core Features & Use Cases - Test Gate: Runs the project's test suite first and blocks any merge or PR if tests fail. - Structured Options: Presents exactly four choices — merge locally, push and create a PR, keep the branch as-is, or discard the work. - Safe Cleanup: Deletes branches and removes git worktrees only when appropriate, requiring typed confirmation before discarding work. - Use Case: After finishing a feature branch in a git worktree, invoke this Skill to verify tests pass, create a pull request with a summary and test plan via gh pr create, and clean up the worktree. ## Quick Start Ask the assistant to finish the current development branch and present the merge, PR, keep, or discard options after verifying tests pass.

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 feature branch after development is complete?▼

Verify the test suite passes first, then check out the base branch, pull latest changes, merge the feature branch, and re-run tests on the merged result. Only delete the feature branch after tests pass on the merge.

How to create a GitHub pull request from the command line?▼

Push the branch with git push -u origin, then run gh pr create with a title and body containing a summary of changes and a test plan checklist. The Skill generates this PR body automatically.

When should I remove a git worktree after finishing a branch?▼

Remove the worktree only after merging locally or discarding the branch. Keep it when creating a pull request or keeping the branch as-is, since the work may still be needed.

What happens if tests fail before merging a branch?▼

The workflow stops immediately and reports the failing tests. No merge, pull request, or cleanup proceeds until all tests pass, preventing broken code from reaching the base branch.

Can I recover a branch after choosing to discard it?▼

No, discarding permanently deletes the branch, its commits, and the worktree. That is why the workflow requires typing 'discard' as explicit confirmation before executing git branch -D.

Related Skills

Explore More Software Engineering Skills→
openaiopenai
5.3k

finishing-a-development-branch

Guides merging, pushing, or keeping a completed development branch with worktree cleanup.

Official
Advanced
az9713az9713
2

land-and-deploy

Merge pull requests, deploy code, and verify production health.

Community
Advanced
erfanzarerfanzar
27

requesting-code-review

Automate pre-commit code review with static checks, linting, and auto-fixes.

Community
Advanced
hung-phanhung-phan

trunk-based-development

Implement a trunk-based development workflow with short-lived branches and feature flags.

Community
Advanced