git-worktree-topology
Skill1 starsChanged 2 months agoNo licenceView on GitHub
Git ref-naming, worktree-isolation, and stacked-PR merge mechanics for running multiple agents in parallel against one repo. Use when planning or dispatching parallel/concurrent subagents that each get their own branch or worktree, when designing a branch-naming scheme for a multi-PR or stacked-PR run, when an agent hits 'cannot lock ref' / 'already exists' on branch creation, or when deciding how to derive a PR's base branch, whether to squash a stacked PR, or whether to force-push into a chain, when a wave dispatches against a base branch cut earlier, or when reading branch or file state another agent's worktree or a merged PR produced. Not about orchestration control flow (dispatch/resume/pause of the agents themselves): only the git/worktree mechanics underneath it.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-styleSkill
- benchmark-code-graphsSkill
- bug-reportSkill
- claims-and-scope-disciplineSkill
- context7-mcpSkill
- dreamSkill
- dual-scoped-review-plansSkill
- improve-memorySkill
- plan-and-reviewSkill
- plan-docsSkill
- plan-rolloutSkill
- reviewSkill
- root-cause-fixSkill
- send-resultsSkill
- session-analysisSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.