finishing-a-development-branch

Guides completion of development branches through merge, pull request, keep, or discard options.

2|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/Grupo-6-ADS-B/FittNutri --skill finishing-a-development-branch-grupo-6-ads-b
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Grupo-6-ADS-B/FittNutri/tree/main/.claude/skills/finishing-a-development-branch
Command: npx skills add https://github.com/Grupo-6-ADS-B/FittNutri --skill finishing-a-development-branch-grupo-6-ads-b

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 process for finishing a development branch so nothing is merged untested or discarded by mistake. ## Core Features & Use Cases - Test Verification Gate: 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 — then executes the chosen workflow with the correct git commands. - Safe Cleanup: Requires typed confirmation before discarding work and cleans up git worktrees only when appropriate. - Use Case: After finishing a feature branch in a git worktree, use this Skill to verify tests pass, create a pull request with a summary and test plan via the GitHub CLI, and clean up the worktree. ## Quick Start Use the finishing-a-development-branch skill to complete my current feature branch now that all 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 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. Each option has a defined git command sequence to follow.

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

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

Should I merge a branch when tests are failing?▼

No. Failing tests block all completion options. Fix the failures first, rerun the test suite, and only proceed with merge or pull request creation once everything passes.

When should I clean up a git worktree after finishing a branch?▼

Remove the worktree only after a local merge or after 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 discard a development branch without losing work accidentally?▼

Require explicit typed confirmation of 'discard' before deletion, showing the branch name, commits, and worktree path that will be removed. Then force-delete the branch with git branch -D and remove the worktree.