git-worktree
Skill4 starsChanged 3 months agoMITView on GitHub
Create a git worktree for isolated branch work by symlinking node_modules and .env files from the main repo — no reinstall. Use when asked to "create a worktree", "add worktree", "work on a branch without reinstalling", "set up worktree for branch". Never run npm/yarn/pnpm install inside the worktree unless package.json changed on the branch.
- Reads credentials
- Installs packages
30 other projects use a version of this.
Adopted by
Most recently taken up by
- aegntic/compound-engineeringtheir own version, first seen Nov 8, 2026
- sbluemin/fleet-harnesstheir own version, first seen Nov 8, 2026
- yht-4403/jc-agent-skillstheir own version, first seen Nov 8, 2026
- yuri-xyz/skillstheir own version, first seen Nov 8, 2026
- iliaal/ai-skillstheir own version, first seen Nov 7, 2026
- eliasjnior/claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use agent-native-architecture, document-review and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CodeWithBehnamSkillagent-native-architecture
Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.
Also in 3 projects that use this
CodeWithBehnamSkilldocument-review
This skill should be used to refine brainstorm or plan documents before proceeding to the next workflow step. It applies when a brainstorm or plan document exists and the user wants to improve it.
Also in 3 projects that use this
MicrosoftSkillgit-commit
Stage user-selected paths, confirm the exact staged set, and create one local Conventional Commit, or generate a commit message for staged changes without committing. Use when you want a guarded commit or a ready-to-paste message.
Also in 3 projects that use this
MicrosoftSkillgrill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Also in 3 projects that use this
OpenAISkillbrainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 4 projects that use this
Other versions30 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 30
- davidondrej/skills★ 4.3ksame name
- iliaal/ai-skills★ 45same name
- sbluemin/fleet-harness★ 17same name
- BackToCimaCoppi/Praxis★ 6same name
- KroxiDev/engineering-skills★ 4same name
- MithunWijayasiri/dotclaude★ 4same name
- CodeWithBehnam/cc-docs★ 2same name
- hmj1026/dhpk★ 2same name
- tsubakimoto/skills★ 2same name
- yuri-xyz/skills★ 2same name
20 more not listed
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 repository38 other files it gives its agents.
- skills/take-ownership/AGENTS.mdAGENTS.md
- bitwarden-cliSkill
- blogpostSkill
- build-in-public-reelSkill
- chrome-devtools-remoteSkill
- chrome-useSkill
- claude-maxSkill
- claude-sessionsSkill
- dev-stackSkill
- dev-workflowSkill
- dev-workflow-supervisorSkill
- duckdns-domainSkill
- flutter-android-releaseSkill
- github-copilot-sessionsSkill
- google-workspace-cliSkill
- hyperagent-eval-skillSkill
- macro-panelSkill
- mermaid2excalidrawSkill
- naste-slaste-styleSkill
- no-github-backlogSkill
- no-pr-backlogSkill
- opencode-apiSkill
- opencodeSkill
- overflowSkill
- prompt-hermes-aiSkill
- reportSkill
- retrospectiveSkill
- secretsmctlSkill
- solo-founder-meta-agentSkill
- solo-founderSkill
- spaceship-dnsSkill
- take-ownership-meta-agentSkill
- take-ownershipSkill
- telegram-cliSkill
- vercel-lfsSkill
- write-agents-mdSkill
- write-skillSkill
- yc-pitch-deckSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Create worktrees that reuse the main repo's installed packages via symlinks.
- Distinctive: line 12
Run from inside the main repo directory.
- Very specific: line 40
Only symlink files that exist in main — the [ -f ...
- Very specific: line 41
Remove when done: git worktree remove "../<branch>".
“Common” is measured: kept by at least 6 in 10 of the 25 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
git-worktree
Create worktrees that reuse the main repo's installed packages via symlinks. Reinstalling is never needed unless the branch changes package.json.
Steps
Run from inside the main repo directory. The main repo's directory name is resolved dynamically — no hardcoded repo name:
BRANCH=$1
MAIN="$(basename "$(git rev-parse --show-toplevel)")" # the main repo's dir name
git fetch origin
# Resolve the remote's default branch (main, master, …) — don't hardcode "main".
BASE="$(git symbolic-ref --quiet --short refs/remotes/origin/HEAD 2>/dev/null)"
[ -n "$BASE" ] || { git rev-parse --verify --quiet origin/main >/dev/null \
&& BASE=origin/main || BASE=origin/master; }
# Create the worktree directly ON the branch — never check out afterwards (that
# would detach HEAD and abandon $BRANCH).
if git show-ref --verify --quiet "refs/heads/$BRANCH"; then
git worktree add "../$BRANCH" "$BRANCH" # existing local branch
else
git worktree add -b "$BRANCH" "../$BRANCH" "$BASE" # new branch off the default
fi
cd "../$BRANCH"
ln -snf "../$MAIN/node_modules" .
ln -snf "../$MAIN/.env" .
[ -f "../$MAIN/.env.prod" ] && ln -snf "../$MAIN/.env.prod" . # only if it existsThe worktree is now checked out on $BRANCH (a new branch off the remote's default branch, or the existing one). The symlinks are relative to the worktree dir, so ../$MAIN/ resolves to the sibling main-repo checkout the worktree was created next to.
Rules
- Never run
npm install/yarn/pnpm installinside the worktree unlesspackage.jsondiffers from main. - Only symlink files that exist in main — the
[ -f ... ]guard skips a missing.env.prod. - Remove when done:
git worktree remove "../<branch>".
Verify
MAIN="$(basename "$(git rev-parse --show-toplevel)")"
ls -la node_modules .env
# node_modules -> ../<MAIN>/node_modules
# .env -> ../<MAIN>/.envDoes 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.

