but

Automate Git version-control tasks using the GitButler CLI.

1|Updated Apr 20, 2026

Search Tags:#git #cli #workflow-automation #gitbutler #branch-management #version-control #commit-management

Ready to run

npx skills add https://github.com/Abstract-Data/mediaite-ghostink --skill but-abstract-data

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: but
Source: https://github.com/Abstract-Data/mediaite-ghostink/tree/main/.cursor/skills/gitbutler
Command: npx skills add https://github.com/Abstract-Data/mediaite-ghostink --skill but-abstract-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

GitButler automates version-control operations to reduce manual git toil across commits, branches, and history edits.

Core Features & Use Cases

Stage and commit with per-branch granularity, branch stacking, and history editing (squash, move, reword, absorb).
Automates PR creation, conflict resolution, and applied/unapplied workspace workflows for complex multi-branch scenarios.
Real-world use: teams coordinate multiple feature branches and stacked work with consistent commit semantics and safe mutation rules.

Quick Start

Install GitButler and begin with 'but status -fv' to inspect state, then follow the non-negotiable rules to drive mutations.

Frequently Asked Questions about but

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

FAQPage Schema

How do I automate Git branch stacking and history editing without manual toil?▼

You can automate Git branch stacking and history editing by running the GitButler CLI, which replaces conventional git commands to handle squash, move, and reword operations with built-in safety checks and consistent commit semantics.

What is the best way to manage multiple stacked feature branches in version control?▼

Managing multiple stacked feature branches is handled through applied and unapplied workspace workflows in GitButler. This approach coordinates complex multi-branch scenarios using per-branch staging granularity and automated conflict resolution.

How do I commit changes to specific branches when working on multiple stacks?▼

To commit changes to specific branches across multiple stacks, use the GitButler CLI with per-branch granularity. It applies frontmatter-driven rules and dependency checks to stage and commit work safely within the correct branch context.

Does GitButler work for automating PR creation and conflict resolution?▼

Yes, GitButler works for automating PR creation and conflict resolution by replacing manual git commands. It drives these tasks through the CLI with safety checks, applying workspace workflows to resolve conflicts across stacked branches.

Can I use GitButler to edit commit history across multiple branches safely?▼

You can use GitButler to edit commit history across multiple branches safely by applying its non-negotiable mutation rules. The CLI enforces safety checks and dependency management during squash, move, and reword operations to prevent history corruption.

Why do I need frontmatter-driven rules for Git workflow automation?▼

You need frontmatter-driven rules for Git workflow automation because they provide the guidance required to drive safe mutations. These rules enforce safety checks and dependency management that prevent errors during complex branch and history edits.