finishing-a-development-branch

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

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/adrianasiam19/ATLAS --skill finishing-a-development-branch-adrianasiam19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/adrianasiam19/ATLAS/tree/main/.agent/skills/finishing-a-development-branch
Command: npx skills add https://github.com/adrianasiam19/ATLAS --skill finishing-a-development-branch-adrianasiam19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementation work is done, developers often face ambiguity about how to integrate the branch safely. This Skill removes that guesswork by verifying tests first, then presenting a structured set of completion options and executing the chosen git workflow without skipping safety checks. ## Core Features & Use Cases - Test Gate Before Integration: Runs the project's test suite (npm test, cargo test, pytest, go test) and blocks any merge or PR if failures exist. - Four Structured Completion Options: Merge locally to the base branch, push and create a GitHub Pull Request via gh CLI, keep the branch as-is, or discard the work with typed confirmation. - Worktree Cleanup: Detects and removes git worktrees for merged or discarded branches while preserving them when work is kept or a PR is opened. - Use Case: After finishing a feature branch with all tests passing, invoke this Skill to get a clear menu of integration choices, then have it execute the merge, PR creation, or safe deletion automatically. ## Quick Start Ask the assistant to finish the current development branch and present the available integration options.

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?▼

First verify the full test suite passes, 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 merged code.

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

Push the feature 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 gh CLI must be installed and authenticated.

Should I delete a git worktree after merging a branch?▼

Remove the worktree only when the branch is merged locally or discarded. If you pushed a pull request or kept the branch for later, preserve the worktree since the work may still need changes.

What happens if tests fail before merging a branch?▼

The merge or pull request process stops immediately. Failing tests must be fixed first, because integrating broken code would introduce failures into the base branch or create a failing PR.

How do I discard a development branch without losing work accidentally?▼

Require explicit typed confirmation before deletion, listing the branch name, commits, and worktree path that will be removed. Then use git branch -D to force-delete the branch and remove the worktree.