Orchestrate GitButler CLI feature lifecycles with plan-driven surgical commits.
npx skills add https://github.com/yspreen/dotfiles --skill butler-flow
Please help me install this Agent Skill. Skill: butler-flow Source: https://github.com/yspreen/dotfiles/tree/main/.agents/skills/butler-flow Command: npx skills add https://github.com/yspreen/dotfiles --skill butler-flow
Orchestrates a complete feature lifecycle from idea to implementation using the GitButler CLI, enabling disciplined branch management and plan-driven commits.
Initiate a feature request, then follow the Butler Flow to name a branch, generate a plan, and perform surgical commits using the but CLI.
High-intent search queries and answers about installing and using this skill.
Feature workflow management uses the GitButler CLI to orchestrate branch creation, enter plan mode, and execute surgical commits. You gather context, name a branch, generate a structured Markdown plan, and verify changes using but diff and but status after each commit.
Plan-driven collaboration for parallel agents uses a structured Markdown plan containing branch info, version control rules, and commit steps to enforce strict isolation. Agents ignore changes not from their own plan and verify outputs using but diff and but status after every surgical commit.
Executing a formal plan document requires entering plan mode via the GitButler CLI and following a structured Markdown plan embedded with exact but commands. The workflow enforces surgical commits and mandates verification using but diff and but status after each commit step.
GitButler CLI supports strict isolation for parallel agents by enforcing plan-driven commits. Agents follow a structured Markdown plan, ignore changes not from their own plan, and verify their specific feature lifecycle outputs using but diff and but status after every commit.
A plan-driven commit workflow is necessary when starting new features or bug fixes in environments with parallel agents. It enforces strict isolation and requires a formal plan document with exact but commands, ensuring surgical commits and verification using but diff and but status.
Feature lifecycle orchestration requires verification after every commit to maintain strict isolation in parallel agent environments. Running but diff and but status after each surgical commit ensures that only changes from your specific structured Markdown plan are applied to the branch.
galliganManage concurrent AI agent operations on GitButler virtual branches.
otrebuMerge a feature branch into main with conflict handling and push.
masrurimzDecompose tasks and coordinate specialist subagents via the Task tool.
drnIdentify the Git commit that introduced a bug using git bisect.
