Manage commits, branches, stacks, and pull requests with the GitButler CLI.
npx skills add https://github.com/titaneric/dotfiles --skill but-titaneric
Please help me install this Agent Skill. Skill: but Source: https://github.com/titaneric/dotfiles/tree/main/dot_agents/skills/gitbutler Command: npx skills add https://github.com/titaneric/dotfiles --skill but-titaneric
but CLI workflows so version control operations stay safe and consistent. ## Core Features & Use Cases - Selective Commits: Commit specific dirty files or individual hunks by CLI ID using but diff and but commit --changes, including one-command branch creation with -c. - History Editing: Amend, squash, reorder, split, and uncommit changes with but amend, but squash, but move, and but uncommit, with rules for handling rewritten commit IDs. - Stacked Branches & PRs: Stack or unstack branches with but move, resolve conflicts via but resolve, and create stack-aware pull requests with but pr new. - Use Case: You have a dirty working tree mixing two unrelated changes. Run but diff to get file and hunk IDs, then chain two but commit calls with --changes to produce two clean, ordered commits on a new branch. ## Quick Start Ask the agent to inspect uncommitted changes with but diff and commit only the selected files to a new branch using the GitButler CLI.High-intent search queries and answers about installing and using this skill.
Run but diff to list uncommitted changes with file and hunk IDs, then pass them to but commit with --changes as comma-separated IDs. A hunk ID uses the form <file-id>:<hunk-id>, such as qs:5, and is not a line range.
Use but move <branch-name> <target-branch-name> with full branch names or branch CLI IDs to stack an existing branch onto another. To unstack, run but move <branch-name> zz, which tears the branch off into its own stack.
No, git write commands like commit, checkout, rebase, merge, and stash break the GitButler workspace model and must be replaced with but equivalents. Read-only git commands such as git log, git blame, and git show remain safe to use.
This indicates a dependency lock: the file was originally committed on another branch, so it cannot be committed on your current branch. Stack your branch onto the owning branch with but move, then commit the file again.
Run but pr new <top-branch-id> -t, which pushes the branch and creates reviews for it and its dependencies in stack order. Stacked PRs must go through but pr so bases and stack footers stay correct; gh pr create loses that metadata.
galliganManage concurrent AI agent operations on GitButler virtual branches.
az0512124155azz-sysSyncs a session branch with its upstream via fetch, rebase, and push.
Knuckles-TeamQuery Git history, diffs, and blame via git_action for audits and reviews.
sduduzogAutomate advanced Git workflows across branches for clean history.