Worktree ops
Skill mike-diff/ai-coding-configs/.cursor/skills/worktree-ops
Multi-agent harness configurations: agent teams, safety hooks, skills and context engineering patterns
npx -y skills add mike-diff/ai-coding-configs --skill worktree-opsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Operational guidance for Cursor's /worktree command. Activates when deciding whether to isolate a task in a dedicated worktree for parallel or risky work.
SKILL.md
1.0 KB, 182 tokens by cl100k_base, as published. Nobody here has run it
/worktree — Task Isolation via Worktrees
Guidance for when and how to use Cursor's worktree isolation feature.
When to use
- Risky refactors that may break the working tree
- Parallel implementations of independent features
- Experimental spikes you want to discard cleanly
- Long-running tasks that shouldn't block the main branch
How it works
/worktreecreates an isolated git worktree with its own branch- Work proceeds independently — no conflicts with main
- When done, merge or cherry-pick back, then clean up the worktree
Best practices
- Name worktrees descriptively:
feat/short-descriptionorfix/issue-ref - Keep worktree lifespan short — merge or discard within a session
- Use
--worktreeflag withcursor agentfor headless runs