setup-worktree
Skill447 starsChanged 3 months agoMITView on GitHub
Set up a new git worktree for this repo by copying gitignored files (bin/) and building server assets so pnpm dev works without errors
- Reads credentials
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
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
- Very specific: line 8
When a new git worktree is created, gitignored files (like the Temporal CLI binary in bin/) are missing and server assets haven't been …
“Common” is measured: kept by at least 6 in 10 of the 3 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
Purpose
When a new git worktree is created, gitignored files (like the Temporal CLI binary in bin/) are missing and server assets haven't been built. Run this skill to get a new worktree ready for development.
Steps
1. Find the main worktree path
git worktree listThe first entry is the main worktree. Use it as $MAIN.
2. Copy .env from the main worktree
MAIN=$(git worktree list | head -1 | awk '{print $1}')
cp $MAIN/.env ./.env3. Build server assets
Builds the frontend into server/ui/assets/ which the Go server embeds. Required for pnpm dev to start.
pnpm build:serverpnpm dev should now start without errors.
Why each step is needed
| Step | Why |
Copy .env | Gitignored — not present in a fresh worktree, needed for dev modes |
pnpm build:server | Runs VITE_API= BUILD_PATH=server/ui/assets/local vite build — without this, pnpm dev fails because the embedded server assets are missing |
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- ralphkrauss/agent-orchestrator★ 4same name
- Jancera/skills★ 1same name
- mauriciovieira/skills★ 1same 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 repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auth-testingSkill
- local-temporalSkill
- proto-codegenSkill
- serverless-worker-awsSkill
- svelte-migrateSkill
- system-nexus-operationSkill
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.