How do I install the Worktree Flow skill?

Run npx skillmds@latest add harshanandak/worktree-flow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Worktree Flow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Worktree Flow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Worktree Flow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Worktree Flow?

harshanandak (@harshanandak) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Worktree Flow by harshanandak — Agent Skill

Name: Worktree Flow
Author: harshanandak

Worktree Flow

Use before starting any Forge code change, and whenever a second agent is about to work in the same repo — creating, entering, or cleaning an isolated worktree. Do not use raw `git worktree add`; it creates a branch and nothing else.

harshanandak 813a102 2.1 KB Updated Sep 17, 2026

File contents

worktree-flow

Two agents in one checkout collide on HEAD mid-task. The isolation is not optional and the primary checkout is not yours. [Forge #6 ×4]

Create

forge worktree create <slug>

Run it from the primary repo root — create and clean are cwd-scoped. forge worktree create does three things raw git worktree add does not: it links the kernel issue, sets up the issue store, and wires dependencies. [Forge #6 ×4]

Then work entirely inside .worktrees/<slug>/.

Two things that bite on Windows

node_modules is a root-only junction. A fresh worktree is missing packages/skills/node_modules; junction it or the skills tests fail on a missing chalk/inquirer.
Long paths. After git worktree remove --force, a leftover directory may need a \\?\-prefixed delete.

Clean

forge clean

Fast-forward local main/master first, or squash-merge detection misses your branch and the worktree is left behind. forge clean has no default-branch guard — run it from the primary root and know which branch you are on.

Working alongside other agents

One agent, one worktree, one PR. Two agents leading the same PR is a correction Harsha has made repeatedly. [Forge #6 ×4]
Parallel agents state file ownership up front, before either starts editing.
Never call another agent dead from one sample. A clean tree and no recent writes also describes an agent between a commit and its next red test. Sample twice, minutes apart, and compare. Any respawn must refuse to edit a contended worktree.
If you are asked to work in the primary checkout while another stream is live, say no and create a worktree.

Done when

Your changes live on a branch inside .worktrees/<slug>/, the primary checkout is untouched, and the worktree either has an open PR or has been cleaned.

---name: worktree-flowdescription: Use before starting any Forge code change, and whenever a second agent is about to work in the same repo — creating, entering, or cleaning an isolated worktree. Do not use raw `git worktree add`; it creates a branch and nothing else.---# worktree-flowTwo agents in one checkout collide on HEAD mid-task. The isolation is notoptional and the primary checkout is not yours. [Forge #6 ×4]## Create```bashforge worktree create <slug>```Run it from the **primary repo root** — create and clean are cwd-scoped.`forge worktree create` does three things raw `git worktree add` does not: itlinks the kernel issue, sets up the issue store, and wires dependencies.[Forge #6 ×4]Then work entirely inside `.worktrees/<slug>/`.## Two things that bite on Windows- **`node_modules` is a root-only junction.** A fresh worktree is missing `packages/skills/node_modules`; junction it or the skills tests fail on a missing `chalk`/`inquirer`.- **Long paths.** After `git worktree remove --force`, a leftover directory may need a `\\?\`-prefixed delete.## Clean```bashforge clean```Fast-forward local `main`/`master` first, or squash-merge detection misses yourbranch and the worktree is left behind. `forge clean` has no default-branchguard — run it from the primary root and know which branch you are on.## Working alongside other agents- One agent, one worktree, one PR. Two agents leading the same PR is a correction Harsha has made repeatedly. [Forge #6 ×4]- Parallel agents state file ownership up front, before either starts editing.- **Never call another agent dead from one sample.** A clean tree and no recent writes also describes an agent between a commit and its next red test. Sample twice, minutes apart, and compare. Any respawn must refuse to edit a contended worktree.- If you are asked to work in the primary checkout while another stream is live, say no and create a worktree.## Done whenYour changes live on a branch inside `.worktrees/<slug>/`, the primary checkoutis untouched, and the worktree either has an open PR or has been cleaned.

Frequently asked questions