igamenovoer/create-git-worktree
skills/devel/create-git-worktree/SKILL.md
Manual invocation only; use only when the user explicitly requests `create-git-worktree` by exact name. Create a clean git worktree for the current repository and symlink reusable local tool-state directories into it.
$ install --global
skillsauthnpx skillsauth add igamenovoer/magic-context create-git-worktreeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 8:07 PM4.5s3 files scanned
SKILL.md
- name:
- create-git-worktree
- description:
- Manual invocation only; use only when the user explicitly requests `create-git-worktree` by exact name. Create a clean git worktree for the current repository and symlink reusable local tool-state directories into it.
Create Git Worktree
Manual invocation only: use this skill only when the user explicitly requests create-git-worktree by exact name.
Create a fresh worktree from the current repository while leaving the active checkout untouched. Prefer the bundled script so branch handling, default paths, and safe symlink rules stay consistent.
Quick Start
Run:
bash scripts/create_worktree.sh [--branch BRANCH] [--path TARGET_PATH] [--link-dir NAME]
Use these defaults unless the user says otherwise:
- Source ref: current branch from
git branch --show-current - Target path:
<repo-root>/.shadow-repo/worktree-<ts> - Timestamp format:
YYYYMMDD-HHMMSSin UTC - Extra symlink dirs: none
If the user specifies a path, use it instead of the default. If the user specifies extra directories to reuse, pass them with repeated --link-dir flags.
Workflow
1. Resolve the source ref
- Use the user-selected branch or ref if provided.
- Otherwise use the current branch.
- If the current checkout is detached and the user did not provide a branch or ref, pause and ask for one.
2. Create the worktree with Git
- Use
git worktree add; do not copy the repository manually. - If the source ref is a local branch that is not checked out in another worktree, create a normal branch worktree.
- If that branch is already checked out elsewhere, create a detached worktree at the branch tip instead. This preserves the requested clean snapshot while avoiding Git's branch checkout conflict.
3. Symlink reusable local-state directories
Consider these default candidates:
.claude.codex.gemini.github.aider.cursor.continue.windsurf.kiro
Apply these rules for each candidate and for any user-requested extra directory:
- Symlink only when the source path already exists in the repo root.
- Skip the path if Git tracks any files under it.
- Do not replace tracked content in the new worktree with a symlink.
4. Handle Pixi projects
- Detect Pixi via
pixi.toml,pixi.lock, or a[tool.pixi]section inpyproject.toml. - If the repo is Pixi-managed and
.pixi/exists as an untracked directory, symlink it into the new worktree.
5. Verify and report
Report:
- The created worktree path
- The source ref used
- The resulting commit
- Whether the worktree is attached to a branch or detached
- Which directories were linked
- Which directories were skipped because they were tracked
Note that git status in the new worktree may show the linked local-state directories as untracked. That is expected.
Resources
scripts/create_worktree.sh: Create the worktree and add the safe symlinks.
Example Prompts
Create a shadow worktree for this repo under .shadow-repo and link the agent home directories.Make a clean worktree of branch release/1.4 at tmp/release-wt and reuse .claude and .pixi.Create a worktree for this repo at /tmp/gig-agents-clean; keep my current uncommitted changes untouched.
Related Skills
igamenovoer/mermaid-graphing
data-ai
VerifiedTrustedCommunity
Create readable Mermaid diagrams inside Markdown files. Use for flowcharts and sequence diagrams that must render cleanly in common Markdown renderers (e.g., GitHub) without horizontal scrolling. Covers fenced mermaid blocks, init/theme styling, label wrapping with <br/>, and sequenceDiagram layout rules (short IDs, wrapped labels, don’t break identifiers).
7SKILL.mdUpdated Apr 5, 2026
igamenovoer/make-program-tutorial
development
VerifiedTrustedCommunity
Manual invocation only; use only when the user explicitly requests `make-program-tutorial` by exact name, OR when the user asks to use a skill to create an SDK/API/library tutorial. Create a clear, reproducible, step-by-step tutorial for a specific API/SDK/library (or a set of functions/classes), with runnable examples, expected outputs, and basic troubleshooting.
7SKILL.mdUpdated Apr 5, 2026
igamenovoer/pixi-make-offline-channel
testing
VerifiedTrustedCommunity
Use when the user wants to create a self-hosted, offline-installable Conda channel (mirror) containing a specific subset of packages using Pixi.
7SKILL.mdUpdated Apr 5, 2026
igamenovoer/pixi-make-cu-build-env
tools
VerifiedTrustedCommunity
Guides the agent to setup a new or existing Pixi environment for compiling C++ and CUDA code. It ensures the correct compilers, toolkits, and CMake configurations are in place for a robust user-space build.
7SKILL.mdUpdated Apr 5, 2026