worktree-setup
Skill4 starsChanged 4 months agoMITView on GitHub
Create a ready-to-work git worktree — branch, deps, local config, green build — and report it.
- Reads credentials
3 other projects use a version of this.
Adopted by
Most recently taken up by
- ysamlan/agent-log-giftheir own version, first seen Oct 25, 2026
- robinebers/skillstheir own version, first seen Jun 25, 2026
- TeamSPWK/novatheir own version, first seen Apr 30, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- robinebers/skills★ 48same name
- ysamlan/agent-log-gif★ 9same name
- TeamSPWK/nova★ 2same 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brandkitSkill
- design-taste-frontendSkill
- effect-best-practicesSkill
- effect-reviewSkill
- effect-tsSkill
- imagegen-frontend-webSkill
- logging-best-practicesSkill
- panelSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Very specific: line 19
Install dependencies: Use the package manager the lockfile implies (bun.lock → bun install, and so on), run inside the worktree.
- Distinctive: line 21
Verify green: Run the project's cheapest defined health check — typecheck, build, or test script — inside the worktree.
≈ “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.
Files
Make a git worktree another agent can start working in immediately, without stumbling over missing dependencies or config. Invoked with a target path and branch name; base ref defaults to HEAD.
Steps
- Preconditions. The repo has at least one commit and the target path does not exist. A worktree checks out committed state only — if the caller's task depends on uncommitted changes, stop and report "commit or stash first".
- Create.
git worktree add <path> -b <branch> [<base-ref>]. - Replicate local config. Copy from the main checkout the untracked files the project needs
to run —
.env,.env.*, and similar gitignored local config. When unsure what is needed, check the project's README and agent instructions for required local files. - Install dependencies. Use the package manager the lockfile implies (
bun.lock→bun install, and so on), run inside the worktree. - Verify green. Run the project's cheapest defined health check — typecheck, build, or test script — inside the worktree. Ready means it passes the same check the main checkout passes.
- Report. Reply with: path, branch, base commit, and which check passed. On any failure, report it verbatim and stop — never hand off a broken worktree as ready.
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.