agentmods.dev

git-worktree-parallel-work

A set of rules for using Git worktrees, which are separate working folders connected to different branches of the same repository. It ensures Git commands and tests run in the folder that owns the intended branch.

In plain words
What is it for?
Use it before running Git commands, Playwright, build tools, or edits on a task, especially when multiple worktrees or parallel branches exist.
Why use it?
It prevents work from landing on the wrong branch or conflicting with another folder that already has the branch checked out. This matters when several tasks are developed in parallel.

Cursor rule for Cursor

248 3d ago A scan 428 tokens original MPL-2.0
View the source file DIGI-UW/OpenELIS-Global-2
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/digi-uw/openelis-global-2/git-worktree-parallel-work
Clone the repo
git clone --depth 1 https://github.com/DIGI-UW/OpenELIS-Global-2

Made for: Cursor.

Per session 428 This file is loaded in full into every session.
When invoked 428 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00428 $0.00428
Opus 5 $0.00214 $0.00214
Sonnet 5 $0.00086 $0.00086
Haiku 4.5 $0.00043 $0.00043

Measured 3d ago against content hash e81f8e6bb647, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-worktree-parallel-work scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/git-worktree-parallel-work.mdc · 32 lines

What it actually says

Git worktrees — parallel work discipline

This repo uses multiple worktrees for parallel work. The Cursor workspace root may not be the tree where the current task’s branch is checked out.

Non‑negotiables

  1. Task = directory first
    Before git commands, Playwright, Maven, or editing “the” branch for a ticket/PR, confirm which worktree path owns that branch (git worktree list).

  2. Never fight the lock
    If branch B is already checked out in worktree W, do not git checkout B in another clone. Use W (cd / absolute paths / open folder)—never create local/* (or other) duplicate branches on the main repo just to unblock checkout.

  3. Shells and tests follow the tree
    Prefix commands: cd <worktree-root> && … for that task. Do not assume Workspace Path is the PR tree when parallel work exists.

  4. One line of work = one branch ref
    PRs track one remote branch (e.g. followup/e2e-runtime-remediation). All commits for that PR must land on that ref’s checkout—not a stray local/… branch on another path.

  5. If unsure
    Run git worktree list, identify the row where B is checked out, and operate only under that path until the user changes scope.

Anti‑patterns

  • Checking out the same branch in two directories.
  • “Sync branches” via inventing local/<name> on the main clone while the real branch lives in ~/.cursor/worktrees/....
  • Running Playwright or CI‑critical commands from the wrong worktree and then debugging “mystery” drift.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 32 lines · 428 tokens per session scan A e81f8e6bb647

Subscribe to this mod's changes

git-worktree-parallel-work is a cursor rule published in the GitHub repository DIGI-UW/OpenELIS-Global-2 (248 stars, last pushed 3d ago), licensed MPL-2.0. It adds 428 tokens to every session, about $0.0021 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflowcarbon-design-systemclinical-laboratorydigital-public-goodsfhirglobal-healthhealth-informatics
Related

Other cursor rules, from other repositories

cursorrules

Use the latest version of Shadcn to install new components, like this command to add a button component.

awbx/fhir-dsl · 45 tokens

angular-20

This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.

angular/angular · 0 tokens

dev-standard

Apache Superset development standards and guidelines for Cursor IDE.

apache/superset · 1,147 tokens

cli-error-handling

CLI command error handling patterns.

prisma/orm · 0 tokens

prefer-direct-imports-over-module-mocks

Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.

prisma/orm · 0 tokens

control-plane-descriptors

Control plane descriptor and instance implementation patterns.

prisma/orm · 0 tokens