skills.rest
donellmccoy
donellmccoyCOMMUNITY
Explore all skills by this author →
𝕏@donellmccoyGitHub

finishing-a-development-branch

Verify tests and present four options for finishing a development branch.

Updated Aug 27, 2026
Search Tags:#git#workflow#merge#dotnet#pull-request#tests#finish-branch
One-click install
npx skills add https://github.com/donellmccoy/ECTSystem --skill finishing-a-development-branch-donellmccoy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/donellmccoy/ECTSystem/tree/main/.github/skills/finishing-a-development-branch
Command: npx skills add https://github.com/donellmccoy/ECTSystem --skill finishing-a-development-branch-donellmccoy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams in finishing a development branch after implementation by validating tests and outlining a structured set of next steps (merge locally, push and create PR, keep the branch, or discard).

Core Features & Use Cases

  • Test-driven finish: Verifies tests and builds before choosing how to integrate work.
  • Structured options: Presents exactly four options for completing or disposing of the feature branch.
  • Safe cleanup: Includes optional branch cleanup and worktree management to keep repos tidy.

Quick Start

  • Run tests to verify status: dotnet test AF.ECT.Tests --no-build --logger "console;verbosity=minimal"
  • Build the solution to validate compile: dotnet build ECTSystem.sln --no-restore
  • Determine the base branch to merge into: git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
  • If tests pass, follow the four options:
  1. Merge back to <base-branch> locally
  2. Push and create a Pull Request
  3. Keep the branch as-is (I'll handle it later)
  4. Discard this work

Frequently Asked Questions about finishing-a-development-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the standard options for finishing a git development branch after tests pass?▼

Finishing a development branch involves choosing from four structured options: merge locally to the base branch, push and create a pull request, keep the branch as-is, or discard the work entirely.

How do I verify my dotnet project before merging a feature branch?▼

Before merging a feature branch, verify your dotnet project by running `dotnet test` to ensure tests pass and `dotnet build` to validate the solution compiles successfully without restoring dependencies.

Does this branch finishing workflow require a specific git base branch?▼

The branch finishing workflow dynamically detects the base branch by checking for a merge-base with either `main` or `master`, ensuring compatibility with various git repository configurations.

What is the best way to clean up a git worktree after completing a feature branch?▼

To clean up a git worktree after completing a feature branch, use the optional worktree management step included in the structured workflow, which safely disposes of the branch and keeps the repository tidy after integration.

Can I push and create a pull request instead of merging my git branch locally?▼

Yes, you can push and create a pull request instead of merging locally; the workflow explicitly presents this as a structured option alongside local merge, keeping, or discarding the branch.

Related Skills

Explore More Software Engineering Skills→
s205109s205109
2

cck-verify

Verify .NET solution builds, tests, formatting, and git status before commits.

Community
Intermediate
sumrae412sumrae412
2

finishing-a-development-branch

Verify tests and present Git branch integration options for merging or cleanup.

Community
Intermediate
mvillmowmvillmow
18

worktree-cleanup

Remove merged or stale git worktrees after verifying a clean state.

Community
Basic
TonyQ-AITonyQ-AI
9

finishing-a-development-branch

Run tests and merge, create pull requests, or delete branches.

Community
Advanced