skills.rest
SleyiW
SleyiWCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Guides completion of development branches through verified merge, pull request, or cleanup options.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementation work is done, developers often merge broken code, forget to verify tests, or accidentally delete work. This Skill enforces a safe, structured completion workflow for Git feature branches. ## Core Features & Use Cases - Test Gate Before Completion: Runs the project's test suite first and blocks any merge or PR if tests fail. - Four Structured Options: Presents exactly four choices—merge locally, push and create a PR, keep the branch as-is, or discard the work. - Safe Discard and Worktree Cleanup: Requires typed confirmation before deleting work and cleans up Git worktrees only when appropriate. - Use Case: After finishing a feature branch with passing tests, use this Skill to decide between merging into main locally or pushing and opening a pull request with a generated summary and test plan. ## Quick Start Use the finishing-a-development-branch skill to verify my tests and help me complete this feature 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 finish a Git feature branch after development?▼

First verify the project's test suite passes, then choose between merging locally into the base branch, pushing and creating a pull request, keeping the branch, or discarding it. Never merge or open a PR while tests are failing.

How to create a pull request from a feature branch using GitHub CLI?▼

Push the branch with git push -u origin <branch>, then run gh pr create with a title and body containing a summary of changes and a test plan checklist. Verify tests pass before pushing.

Should I merge locally or create a pull request?▼

Merge locally when working solo or without a review process; create a pull request when the team needs code review or CI checks. Both paths require passing tests, and local merges should re-run tests on the merged result.

When should Git worktrees be cleaned up after merging?▼

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

How do I safely delete a Git branch without losing work?▼

Require explicit typed confirmation listing the branch name, commits, and worktree path before deletion. Use git branch -D only after confirmation, and never delete work without showing what will be permanently removed.

Related Skills

Explore More Software Engineering Skills→
JerrylalalaJerrylalala
6

finishing-a-feature

Verifies tests and integrates completed feature branches via merge, pull request, or push.

Community
Intermediate
greencmgreencm
1

land-and-deploy

Merge pull requests, run CI tests, and deploy to production with canary checks.

Community
Advanced
meta-pytorchmeta-pytorch
2.5k

pre-submit-pr

Automate pre-submit PR validation with linting, tests, and RFC analysis.

Official
Intermediate
modu-aimodu-ai
4

moai-ref-git-workflow

Standardize Git workflows, branch strategies, and PR templates across projects.

Official
Advanced