skills.rest
mattniedelman
mattniedelmanCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Validate tests and present merge, PR, keep, or discard options for a development branch.

1|Updated Dec 25, 2017
Search Tags:#git#worktree#merge#branch#pull-request#tests
One-click install
npx skills add https://github.com/mattniedelman/dotfiles --skill finishing-a-development-branch-mattniedelman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/mattniedelman/dotfiles/tree/main/dot_augment/skills/finishing-a-development-branch
Command: npx skills add https://github.com/mattniedelman/dotfiles --skill finishing-a-development-branch-mattniedelman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers finish work on a development branch by ensuring tests pass and guiding a clean, auditable merge/PR process.

Core Features & Use Cases

  • Verify tests: runs the project's test suite to ensure changes are safe to integrate.
  • Present options: after validation, outputs exactly four choices to decide how to proceed.
  • Execute decisions: performs the selected workflow (merge locally, push/PR, keep, or discard) and handles cleanup.

Quick Start

Run the skill to assess the current feature branch and present merge options. Then choose one of:

  1. Merge back to the base branch locally
  2. Push and create a Pull Request
  3. Keep the branch as-is
  4. Discard this work

After choosing, the skill will apply the action and clean up as needed.

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 finish a git branch and merge it back to the base branch?▼

To finish a git branch, you verify tests pass and then select from four options: merge locally, push for a pull request, keep the branch, or discard the work. The skill executes the chosen action and handles post-action cleanup.

What is the best way to verify tests before creating a pull request?▼

The best way to verify tests before a pull request is to run the project's test suite on your development branch. This validates that code changes are safe to integrate before you push and create a PR.

Can I discard my git branch changes after tests fail?▼

Yes, you can discard your git branch changes. After running tests, the workflow explicitly offers the option to discard this work, allowing you to abort the integration and clean up the failed branch.

Does finishing a development branch handle worktree cleanup?▼

Yes, finishing a development branch handles cleanup. After you execute a decision to merge, create a pull request, or discard, the process automatically manages the required post-action cleanup.

How do I keep a development branch as-is without merging?▼

To keep a development branch as-is without merging, you select the explicit keep option presented after test validation. This pauses the integration process while preserving your current worktree state.

Related Skills

Explore More Software Engineering Skills→
lagz0nelagz0ne
2

finishing-a-development-branch

Verify tests and present merge, PR, or cleanup options for a development branch.

Community
Basic
tkerseytkersey
66

fin

Finish GitHub pull requests by updating branches, monitoring CI, and squash-merging.

Community
Advanced
kirvinkirvin

sync

Fetch upstream changes and rebase the current Git branch onto them.

Community
Intermediate
dzineerdzineer

update-2-git-with-diff

Generate a Git diff, create a pull request, and merge into the main branch.

Community
Intermediate