parallel-worktrees
Skill0 starsChanged 4 months agoMITView on GitHub
Split substantial work into isolated git worktrees so coding, tests, docs, review, or experiments can proceed in separate lanes without contaminating the main checkout.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- mqmalagris/agent-skillstheir own version, first seen Nov 5, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 3, 2026
- TheBeardedBearSAS/claude-crafttheir own version, first seen Oct 29, 2026
- rohitg00/pro-workflowtheir own version, first seen Sep 29, 2026
- chinthakat/agent-skillstheir own version, first seen Sep 21, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- rohitg00/pro-workflow★ 2.9ksame name
- theexperiencecompany/gaia★ 325same name
- TheBeardedBearSAS/claude-craft★ 108same name
- paureis/pau-skills★ 2same name
- chinthakat/agent-skills★ 0same name
- mqmalagris/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- adr-logSkill
- adversarial-reviewSkill
- ai-writing-detoxSkill
- autonomous-video-pipelineSkill
- browser-tutorial-videoSkill
- codex-execution-packSkill
- continuity-ledgerSkill
- github-mobile-opsSkill
- github-seoSkill
- idea-validationSkill
- illustration-promptSkill
- issue-control-loopSkill
- justdoitSkill
- lazy-seniorSkill
- long-context-dispatchSkill
- openclaw-councilSkill
- playwrightSkill
- product-councilSkill
- product-shapingSkill
- public-artifact-laneSkill
- readme-generatorSkill
- screenshotSkill
- session-to-postSkill
- spec-bundleSkill
- spreadsheetSkill
- spreadsheet-tabular-analysisSkill
- spreadsheet-xlsx-editSkill
- tool-scoutSkill
- transcribe-basicSkill
- transcribe-diarizeSkill
- transcribeSkill
- triage-findingSkill
- video-builderSkill
- video-render-runSkill
- video-spec-builderSkill
- visual-explainerSkill
- work-shapingSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Do not use when: there is only one lane, one owner concern, or the split would be process theater.
- Distinctive: line 14
Use git worktrees as clean execution lanes for substantial multi-track work without inventing extra repos or runtime layers.
- Very specific: line 18
Create dedicated worktrees on dedicated codex/ branches, never directly on the main branch.
- Distinctive: line 24
No lane starts on the main branch or in an unsafe directory.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Parallel Worktrees
Metadata
- Trigger when: the work is substantial and has truly separable lanes that can benefit from isolation.
- Do not use when: there is only one lane, one owner concern, or the split would be process theater.
Skill Purpose
Use git worktrees as clean execution lanes for substantial multi-track work without inventing extra repos or runtime layers.
Instructions
- Confirm that the work really splits into separate owner concerns such as implementation, tests, docs, review, or experiment. Prefer two or three lanes maximum.
- Create dedicated worktrees on dedicated
codex/branches, never directly on the main branch. The command pattern isgit worktree add /absolute/path/to/lane -b codex/<lane-name> <base-ref>. Record each lane’s purpose and shared source of truth before work starts. - Merge or clean up only after each lane has a clear result and no ownership confusion remains. Use
git worktree remove /absolute/path/to/laneonly when the lane is intentionally merged, parked, or discarded.
Non-Negotiable Acceptance Criteria
- Worktrees are for isolation, not orchestration theater.
- Shared decisions live in one durable place such as an issue, brief, or
CONTINUITY.md. - No lane starts on the main branch or in an unsafe directory.
- Cleanup does not happen until the lane outcome is explicit.
Output
- A lane list with branch name, worktree path, owner concern, and purpose.
- The shared source-of-truth artifact for cross-lane decisions.
- Cleanup status for each lane: active, merged, parked, or removed.
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
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.