skills.rest
lookatitude
lookatitudeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

guild-finish-branch

Present merge and cleanup options after verifying tests and determining a base branch.

6|Updated Apr 24, 2026
Search Tags:#git#workflow#verification#merge#branch-management#pull-request#finish-branch
One-click install
npx skills add https://github.com/lookatitude/guild --skill guild-finish-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: guild-finish-branch
Source: https://github.com/lookatitude/guild/tree/main/skills/fallback/finish-branch
Command: npx skills add https://github.com/lookatitude/guild --skill guild-finish-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams to finalize development work by ensuring tests pass and presenting a clear set of next steps for integration, review, or cleanup.

Core Features & Use Cases

  • Structured decision prompts: After verification, the skill presents four explicit options to finalize the work.
  • Gate-driven workflow: It enforces test verification and determines an appropriate base branch before merging.
  • Branch lifecycle handling: Supports local merge, remote PR creation, branch retention for later review, or clean discard of the feature branch.
  • Integration touchpoints: Integrates with guild:execute-plan to align with the overall lifecycle.

Quick Start

Trigger this skill after all lanes report DONE and tests pass to present the four merge/cleanup options.

Frequently Asked Questions about guild-finish-branch

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

FAQPage Schema
How do I finalize a git feature branch after tests pass?▼

To finalize a git feature branch after tests pass, you can use a structured workflow that validates tests, determines the base branch, and presents explicit merge, push, discard, or retention options for branch cleanup.

What is the best way to automate branch cleanup and merge decisions?▼

Automating branch cleanup and merge decisions requires a gate-driven workflow that verifies tests and determines the appropriate base branch before offering concrete actions like local merge, remote PR creation, or clean branch discard.

How does gate-driven branch verification work before a pull request?▼

Gate-driven branch verification works by enforcing test validation and determining an appropriate base branch before allowing a pull request, ensuring that only verified code progresses to integration or review.

Can I keep a feature branch locally instead of merging it immediately?▼

Yes, you can keep a feature branch locally instead of merging immediately, as branch lifecycle management supports retaining completed branches for later review alongside options for local merge, remote PR, or discard.

When should I discard a feature branch instead of creating a pull request?▼

You should discard a feature branch instead of creating a pull request when verification fails or the work is no longer needed, utilizing the clean discard option to remove the branch without integration.

Related Skills

Explore More Software Engineering Skills→
benjgradbenjgrad

finishing-a-development-branch

Verify tests pass, then merge locally, open a PR, keep, or discard a Git branch.

Community
Advanced
the-agency-aithe-agency-ai
39

Post-Merge

Verify merged pull requests, merge origin updates, and create GitHub releases.

Official
Advanced
ronniepinnellronniepinnell

pipeline

Orchestrate development milestones and epics across Linear and GitHub.

Community
Advanced
raas-devraas-dev
19

finishing-a-development-branch

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

Official
Intermediate