finishing-a-development-branch

Verify tests and present merge, PR, or cleanup options for Git branches.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/cill-i-am/task-tracker --skill finishing-a-development-branch-cill-i-am
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/cill-i-am/task-tracker/tree/main/.agents/skills/finishing-a-development-branch
Command: npx skills add https://github.com/cill-i-am/task-tracker --skill finishing-a-development-branch-cill-i-am

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates the finalization of development work by verifying tests pass and guiding the merge/cleanup workflow.

Core Features & Use Cases

  • Verify tests pass before presenting options.
  • Determine the appropriate base branch for merge.
  • Present exactly four options: merge locally, push and create a PR, keep the branch as-is, or discard the work.
  • Execute the chosen option and perform necessary cleanup.

Quick Start

Tell me you finished the feature branch and I will guide you through choosing and executing the next steps for merge, PR, or cleanup.

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 feature branch and choose between merging or creating a pull request?

To finish a Git feature branch, you can use a guided workflow that verifies tests pass, then presents options to merge locally, push and create a pull request, keep the branch, or discard the work.

What is the best way to automate branch cleanup after development is complete?

Automating branch cleanup involves running project tests, selecting a finalization action like a local merge or pull request, and then automatically removing the completed development branch.

Does finishing a development branch require a specific Git environment or test setup?

Finishing a development branch requires a working Git environment, repository access, and the project's configured test command to verify results before presenting merge or cleanup options.

Can I discard a Git feature branch automatically if I no longer need the changes?

Yes, you can discard a Git feature branch automatically by selecting the discard option provided during the guided branch finalization workflow, which removes the unwanted work.

How does the workflow determine the appropriate base branch for a local merge?

The workflow determines the appropriate base branch for a local merge by analyzing the repository structure during the branch finalization process before executing the merge and cleanup.