.agents/skills/git-branch-mixer/SKILL.md
Manage git branch mixes and run mixdowns using ggmx and ggmxd. Use when the user says things like "add this branch to the mix", "remove a branch from the mix", "show the mix", "mix down the branches", or "run a mixdown".
npx skillsauth add aspiers/git-config git-branch-mixerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
ggmx (git mix) configures named sets of branches to merge together.
ggmxd (git mixdown) executes a mixdown — resetting a target branch to a
base and merging all the other branches in.
The typical use case is testing a combination of feature/bugfix branches together via a throw-away temporary working branch.
ggmxggmx # show all configured mixes
ggmx <target> # show branches in mix for <target>
ggmx <target> A B C # set mix for <target> to branches A, B, C
# (first branch is the base)
ggmx [<target>] +D [-B] # add D to / remove B from mix for <target>
# (defaults to 'working' if <target> omitted)
ggmx -d <target> # delete the mix for <target>
Mixes are stored in git config under mixdown.<target>.
You can also edit them directly with git config --edit.
ggmxdggmxd # run mixdown using config for default target ('working')
ggmxd -b <target> # run mixdown using config for <target>
ggmxd BASE B1 [B2 ...] # explicit mixdown: reset to BASE, merge B1, B2...
ggmxd -b <target> BASE B1 ... # explicit mixdown into named target branch
Always pass -c / --checkout to leave the target branch checked out
after the mixdown, ready for testing:
ggmxd -c # mixdown from config, stay on target branch
ggmxd -c BASE B1 B2 # explicit mixdown, stay on target branch
Without -c, ggmxd restores your previously checked-out branch after
completing the mixdown. Use this when you want to rebuild the mix in the
background without switching away from your current branch.
ggmxd -s STRATEGY # set merge strategy (default: octopus)
# use e.g. -s recursive for sequential merges
# with conflict resolution shells between each
After any ggmx operation that modifies a mix (adding, removing, or setting
branches), always ask the user whether they want to run a mixdown now.
# One-time setup: configure the mix for the 'working' target branch
ggmx working main feature/foo bugfix/bar
# Add another branch later
ggmx +feature/baz
# Run the mixdown and stay on the result for testing
ggmxd -c
# Rebuild after rebasing one of the branches
ggmxd -c
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.