Creates and validates Git branch names under a trunk-based branching model.
npx skills add https://github.com/kieranpotts/skills --skill branch-kieranpotts
Please help me install this Agent Skill. Skill: branch Source: https://github.com/kieranpotts/skills/tree/main/skills/branch Command: npx skills add https://github.com/kieranpotts/skills --skill branch-kieranpotts
dev, test, ready), a short-lived temp/* branch, a long-lived epic/* branch, or directly on dev. - Regex Validation: Checks branch names against a strict kebab-case naming regex and reports the exact rule each failing name violates. - Deterministic Branch Creation: Cuts temp/* and epic/* branches from the tip of dev only, verifying ancestry with git merge-base and changing nothing else in the repository. - Use Case: Before starting a bug fix, ask the agent to create a branch for the work; it classifies the change, forms a name like temp/178-fix-auth-timeout, validates it, and cuts it from dev. ## Quick Start Ask the agent to create a branch for the work you are about to start, optionally including an issue identifier to prefix the branch name.High-intent search queries and answers about installing and using this skill.
Classify the work first, then form a lowercase hyphen-delimited name like temp/42-add-search-endpoint and validate it against the naming regex. Cut the branch from the dev trunk using git switch --create so it starts at the current tip of dev.
It is a model with permanent append-only trunks (dev, test, ready) that are fast-forwarded, plus short-lived temp branches for single-focus changes and long-lived epic branches for coordinated work. All changes originate on dev and flow forward through test to ready.
Use an epic branch for long-lived multi-contributor work that cannot be continuously integrated, such as major refactoring or replatforming. Use a temp branch for a single-focus change of a few commits, and no branch at all for one or two commits.
No. It only names, validates, and creates branches, then stops. Committing, merging, releasing, and deleting integrated branches are handled by separate skills or manual steps.
The skill stops and reports that the required dev trunk is missing rather than cutting a branch from whatever trunk exists. The user then decides whether to establish dev or work outside this branching model.
humansysInitialize epic directories, briefs, and tracker entries for new epics.
saxonthuneMerge trunk_claude* worktree branches into trunk and sync with origin.
NIMBUS-MXIdentify stale, merged, and orphaned Git branches for prioritized cleanup.
sddevelopment-beEnforce trunk-based development workflows on the main branch for agent-first collaboration.