skills.rest
ingbyr
ingbyrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

finishing-a-development-branch

Validate tests, detect the base branch, and finish Git development branches via four options.

2|Updated Apr 3, 2026
Search Tags:#git#testing#cleanup#merge#branch-management#pull-request
One-click install
npx skills add https://github.com/ingbyr/lzcode --skill finishing-a-development-branch-ingbyr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/ingbyr/lzcode/tree/main/packages/desktop/src-tauri/lz-assets/skills/finishing-a-development-branch
Command: npx skills add https://github.com/ingbyr/lzcode --skill finishing-a-development-branch-ingbyr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides and automates the completion of development work by verifying tests, selecting an appropriate integration path, and cleaning up artifacts after merge.

Core Features & Use Cases

  • Test verification: Run and confirm that all tests pass before finalizing the branch.
  • Base-branch determination: Detects the correct base branch (e.g., main or master) for the merge.
  • Structured options: Presents exactly four options for finishing the work: merge locally, push and create PR, keep as-is, or discard.
  • Cleanup workflow: Removes worktrees and obsolete branches once the operation completes.

Quick Start

Confirm tests pass and choose one of the four options to finish this branch.

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 development branch safely?▼

Finishing a git development branch safely involves validating tests, determining the base branch, and choosing a structured merge option to ensure safe integration and cleanup of obsolete branches.

What is the best way to manage branch cleanup after a merge?▼

Branch cleanup after a merge is best handled by a structured workflow that removes worktrees and obsolete branches once the selected merge or pull request operation completes successfully.

Can I create a pull request and keep my feature branch instead of merging locally?▼

Yes, you can create a pull request and keep your feature branch. A structured branch finishing workflow presents multiple options, allowing you to push the branch, create a PR, or keep the branch as-is instead of merging locally.

Does test verification happen before or after selecting a merge option?▼

Test verification happens before selecting a merge option. The workflow enforces an end-to-end process where tests must pass first, followed by base-branch detection, before presenting the four structured completion options.

How do I discard a git branch without leaving obsolete worktrees?▼

To discard a git branch without leaving obsolete worktrees, select the discard option within a structured finishing workflow. This ensures the branch is safely discarded and triggers the post-merge cleanup process to remove leftover artifacts.

Related Skills

Explore More Software Engineering Skills→
good-ideagood-idea
3

using-git-worktrees

Create Git worktrees for isolated feature development and cleanup optionally deleting branches.

Community
Intermediate
tachyon-beeptachyon-beep
14

cicd-pipeline-architecture

Architect CI/CD pipelines with deployment strategies, test gates, and rollback mechanisms.

Community
Advanced
doanchienthangdevdoanchienthangdev
4

finishing-development-branches

Enforce quality gates, clean Git history, and prepare pull requests.

Community
Intermediate
pkuppenspkuppens

maintenance-cleanup

Clean up merged branches, worktrees, GitHub Actions runs, and tmp directories.

Community
Intermediate