unity-switch-worktree
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Restarts the Unity Editor on a different project path — closes the currently-running Editor, launches it on the target worktree, waits for the new Editor's stdio bridge to register, and rebinds the MCP session to the new instance so `mcp__UnityMCP__*` tool calls route correctly. Use when the user says "switch Unity to <path>", "open Unity on the #NNN worktree", "restart Unity on this worktree", "point Unity at the other branch", or when Play-mode / MCP-driven work has to happen on a branch different from where the Editor is currently open. Especially useful for git-worktree workflows where Steam / networking / lobby PRs live on separate branches and need Editor-driven verification one at a time.
In this repository29 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- address-reviewSkill
- coding-principlesSkill
- dev-loopSkill
- dispatchSkill
- harden-permissionsSkill
- mermaid-checkSkill
- mockup-parity-loopSkill
- mppm-resetSkill
- netcode-checkSkill
- pr-descriptionSkill
- pr-reviewSkill
- pr-screenshotSkill
- pr-sweepSkill
- pr-videoSkill
- run-playmodeSkill
- scene-wireSkill
- ship-issueSkill
- start-taskSkill
- unity-buildSkill
- unity-e2e-verifySkill
- unity-editor-upSkill
- unity-iterateSkill
- unity-local-multiplayerSkill
- unity-mcp-setupSkill
- unity-new-projectSkill
- unity-smart-mergeSkill
- unity-start-taskSkill
- unity-testSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 5 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
12
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.

