skills.rest
cjennings
cjenningsCOMMUNITY
Explore all skills by this author →
Website𝕏@craigjenningsGitHub

finish-branch

Run verification and present four git branch wrap-up outcomes.

Updated Aug 23, 2026
Search Tags:#git#workflow#verification#worktree#merge#pull-request#finish-branch
One-click install
npx skills add https://github.com/cjennings/rulesets --skill finish-branch-cjennings
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finish-branch
Source: https://github.com/cjennings/rulesets/tree/main/finish-branch
Command: npx skills add https://github.com/cjennings/rulesets --skill finish-branch-cjennings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing a feature branch cleanly after development, with an explicit, deterministic set of outcomes to choose from.

Core Features & Use Cases

  • Runs verification (tests, lint, typecheck) before presenting wrap-up options.
  • Offers four explicit outcomes: merge locally, push and open PR, keep as-is, or discard.
  • Handles git worktree cleanup according to the chosen outcome and preserves worktrees when needed.

Quick Start

Run /finish-branch after verification and select one of the four outcomes.

Frequently Asked Questions about finish-branch

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

FAQPage Schema
How do I finalize a git feature branch with verification before merging?▼

To finalize a git feature branch, this workflow runs tests, lint, and typecheck verification first, then presents four deterministic outcomes: merge locally, push and open a PR, keep as-is, or discard.

What's the best way to clean up a git worktree after finishing a feature branch?▼

The best way to clean up a git worktree after finishing a branch is selecting one of four wrap-up outcomes, which handles worktree cleanup automatically while preserving worktrees when needed.

Can I choose to keep my feature branch as-is instead of merging or discarding it?▼

Yes, you can keep your feature branch as-is. When finalizing your branch, keeping it unchanged is one of the four explicit outcomes offered alongside merging, opening a PR, or discarding.

Does finishing a feature branch enforce governance and commit standards before integration?▼

Finishing a feature branch enforces governance by referencing verification.md, commits.md, and review-code, ensuring tests, lint, and typecheck pass before presenting the four wrap-up outcomes.

Why should I run verification before opening a pull request from my feature branch?▼

You should run verification before opening a pull request because this workflow enforces tests, lint, and typecheck to pass first, ensuring code quality before you push and open a PR.

How do I discard a feature branch and clean up its worktree safely?▼

To discard a feature branch safely, select the discard outcome from the four-option wrap-up workflow, which removes the branch and handles associated git worktree cleanup deterministically.

Related Skills

Explore More Software Engineering Skills→
GantisStormGantisStorm
6

code-quality

Run type checking and linting on staged code changes via start.sh.

Community
Basic
oxieoxie

staging-deployment-phase

Automate staging deployment with auto-merge for merged pull requests.

Community
Intermediate
different-aidifferent-ai
63

worktree-workflow

Create task-specific Git worktrees, initialize submodules, commit, and push changes.

Official
Intermediate
ytqhytqh

finishing-a-development-branch

Integrate a finished development branch by choosing one of four Git workflow options.

Community
Basic