GitButler Complete Branch

Automate GitButler virtual branch completion with safety snapshots and no-ff merges.

28|1|Updated Aug 30, 2025
One-click install
npx skills add https://github.com/outfitter-dev/agents --skill gitbutler-complete-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GitButler Complete Branch
Source: https://github.com/outfitter-dev/agents/tree/main/gitbutler/skills/complete-branch
Command: npx skills add https://github.com/outfitter-dev/agents --skill gitbutler-complete-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrating completed work from GitButler virtual branches into the main codebase can be a delicate process, prone to conflicts or unintended history changes. This Skill provides a guided, safe workflow to ensure smooth integration and cleanup.

Core Features & Use Cases

  • Safety Snapshots: Create a backup of your workspace before any integration, allowing for easy recovery.
  • Guided Merge Workflows: Follow step-by-step instructions for direct merges to main or pull request-based integrations.
  • Error Recovery: Provides clear solutions for common issues like merge conflicts, push rejections, and accidental integrations.
  • Use Case: After completing a new feature on a virtual branch and ensuring all tests pass, use this Skill to safely merge your changes into the main branch, preserving history and cleaning up the virtual branch.

Quick Start

Complete the 'feature-auth' virtual branch and merge it into 'main' using the direct merge workflow, ensuring a safety snapshot is created first.

Frequently Asked Questions about GitButler Complete Branch

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

FAQPage Schema
How do I safely merge a GitButler virtual branch into main?

Safely merge virtual branches by creating a safety snapshot first, then following GitButler's guided workflow for direct merges or pull requests. The Skill automates prerequisite validation, applies --no-ff merges to preserve history, and handles post-merge cleanup automatically.

What happens if a merge conflict occurs during branch integration?

Merge conflicts trigger GitButler's error recovery workflow, which provides clear solutions and guides you through resolution. The safety snapshot created beforehand allows easy recovery if integration fails.

Can I use GitButler's merge workflow with stacked branches?

Yes, the Skill supports stacked branches in its merge orchestration logic. It validates prerequisites across the stack, executes merges in sequence, and manages cleanup for dependent branches after integration into main.

How do I clean up virtual branches after merging to main?

Post-merge cleanup is automated as part of the Skill's workflow after successful integration. Virtual branches are removed following the --no-ff merge, and the workspace is reset to reflect main's updated state.

What pull request workflows does GitButler's merge process support?

The Skill accommodates PR-based integration workflows as an alternative to direct merges. It handles push operations, PR metadata, and cleanup procedures while maintaining the same safety snapshot and prerequisite validation steps.

Do I need tests to pass before using the merge workflow?

Yes, the Skill requires tests to pass as a prerequisite before branch completion. Prerequisites validation ensures all checks succeed, reviews are approved, and the workspace is ready before merge orchestration begins.