agentleFS
Tamircohen28Tamircohen28/tamirs-superpowers/.cursor/rules/git-worktree-agent-workflow.mdc

tamirs-superpowers / rules

Cursor rule2 starsChanged 3 months agoMITView on GitHub

Objective/worker/integration worktrees — provider is metadata, not path identity. Canonical: rules/dev/git-worktree-agent-workflow.md

The file

Files
git-worktree-agent-workflow.mdc
---
description: "Objective/worker/integration worktrees — provider is metadata, not path identity. Canonical: rules/dev/git-worktree-agent-workflow.md"
alwaysApply: false
globs: ".agent-worktrees/**/*,.claude/.worktrees/**/*,.cursor/.worktrees/**/*,.codex/.worktrees/**/*"
---

<!-- GENERATED FILE — DO NOT EDIT.
     Source:    rules/dev/git-worktree-agent-workflow.md (frontmatter + summary: platforms/cursor/rules.map.json)
     Generator: scripts/build-cursor-rules.sh
     Regenerate: make cursor-rules -->

# Git Worktree Agent Workflow

Canonical rule: `rules/dev/git-worktree-agent-workflow.md`. Read it before creating any worktree — the summary below is orientation only.

One objective → zero or more worker worktrees → one integration worktree. The path and branch encode the **objective and task**, never the provider.

```text
.agent-worktrees/<objective>/{integration,task-001,task-002}
main → objective/<slug> → worker/<slug>/NNN
```

A worker ends at **commit + handoff**, never at a PR. Delivery happens once, from the integration worktree.

## Cursor-specific

Cursor has no built-in worktree tool and no `EnterWorktree` equivalent — create worktrees explicitly before editing tracked files from an agent session:

```bash
skills/dev-workflow/_shared/scripts/resolve-worktree.sh --objective <slug> --task 001
```

Legacy `.cursor/.worktrees/<name>` worktrees remain valid and are never orphaned; `resolve-worktree.sh --list` shows them and `--migrate` moves one opt-in.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.