branch

Create worktree-based feature, fix, or hotfix branches with Linear integration.

6|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/withpiper/pipekit --skill branch-withpiper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch
Source: https://github.com/withpiper/pipekit/tree/main/skills/branch
Command: npx skills add https://github.com/withpiper/pipekit --skill branch-withpiper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start any unit of work by creating a worktree and a branch, with optional Linear integration.

Core Features & Use Cases

  • Create feature, fix, or hotfix branches backed by dedicated worktrees.
  • Link branches to Linear issues to sync status and context.
  • Rename workspaces automatically for clear context.

Quick Start

Run /branch <name> to create a new worktree-backed branch and optionally link it to a Linear issue.

Frequently Asked Questions about branch

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

FAQPage Schema
How do I create a git worktree and link it to a Linear issue?

To create a git worktree and link it to Linear, run a single command to generate a worktree-backed branch, which then optionally syncs status and transitions the Linear issue state automatically.

Can I create different types of branches like feature or hotfix branches using git worktrees?

Yes, you can create feature, fix, and hotfix branches using git worktrees, with validation enforcing correct base branch selection and automated workspace renaming for clear project context.

What is the best way to automate Linear status transitions when starting a new branch?

Automating Linear status transitions when starting a new branch involves creating a worktree-backed branch that optionally checks Linear status and automatically transitions the issue state during setup.

Does setting up a git worktree require manually renaming workspaces?

No, setting up a git worktree does not require manually renaming workspaces because the process includes automatic workspace renaming to maintain clear context across feature, fix, and hotfix workflows.

Why does base-branch validation matter when creating worktree branches?

Base-branch validation matters when creating worktree branches because it enforces correct parsing and prevents unstable starting points, ensuring your feature, fix, or hotfix workflows branch from the appropriate base.