using-git-worktrees
Create Isolated Git Worktrees Safely
Concurrent branch work can disrupt the current workspace and hide baseline failures. This skill creates an isolated worktree with directory checks, setup guidance, and test verification.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "using-git-worktrees" from https://skillstore.io/skills/davila7-using-git-worktrees.md and its manifest at https://skillstore.io/api/skills/davila7-using-git-worktrees/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "using-git-worktrees". Create a worktree for the authentication feature.
Expected outcome:
Selected the existing project-local worktree directory and confirmed that Git ignores it. Approval is required before creating the feature branch.
Using "using-git-worktrees". Prepare an isolated workspace and verify the baseline.
Expected outcome:
- The worktree was created at the approved location.
- The detected setup command was approved and completed.
- The baseline test suite passed with no failures.
Using "using-git-worktrees". Set up three worktrees for parallel tasks.
Expected outcome:
Prepared distinct destinations and branch names for all three tasks. Each setup and test action remains subject to separate approval.
Security Audit
High RiskThe static findings are false positives caused by Markdown formatting, documented Git commands, dedicated worktree paths, and standard error redirection. However, the skill automatically runs repository-controlled setup and test commands, and it may commit a .gitignore change without explicit approval.
Confirmed security concerns (2)
Risk Factors
⚙️ External commands (26)
📁 Filesystem access (13)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/davila7-using-git-worktrees/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/davila7-using-git-worktrees?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/davila7-using-git-worktrees?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/davila7-using-git-worktrees/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/davila7-using-git-worktrees.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
davila7. (2026). using-git-worktrees security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/davila7-using-git-worktrees/audits/9BibTeX citation
@techreport{davila7-davila7-using-git-worktrees-2026,
author = {davila7},
title = {using-git-worktrees security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/davila7-using-git-worktrees/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "using-git-worktrees security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "davila7"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/davila7-using-git-worktrees/audits/9"
identifiers:
- type: other
value: "skillstore:davila7-using-git-worktrees:audit:9"
description: "Skillstore immutable audit report identifier"
Compare variants
9 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
zhanlincui-using-git-worktrees
2026-08-21
doyajin174-using-git-worktrees
2026-08-21
codingcossack-using-git-worktrees
2026-08-21
dyai2025-using-git-worktrees
2026-08-21
obra-using-git-worktrees
2026-08-21
cygnusfear-using-git-worktrees
2026-08-21
sickn33-using-git-worktrees
2026-08-21
davila7-using-git-worktrees
2026-08-21
cycleaddict-using-git-worktrees
2026-08-21
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Isolate Feature Development
Create a separate workspace for a feature while preserving the current branch and working tree.
Run Parallel Agent Tasks
Give each coding agent a separate branch workspace to reduce file and branch interference.
Verify a Clean Starting Point
Install approved dependencies and run baseline tests before implementing a planned change.
Try These Prompts
Create an isolated Git worktree for branch <branch-name>. Show the selected location and ask before running setup commands.
Prepare a worktree for <feature>. Check existing worktree directories and CLAUDE.md, verify ignore rules, then propose the creation command.
Create a worktree for <branch-name>. Identify setup and test commands, explain their effects, request approval, and report baseline results.
Plan isolated worktrees for <task-list>. Avoid branch and path conflicts, validate each destination, and provide a status summary for every task.
Best Practices
- Confirm the worktree destination and branch name before creation.
- Verify project-local worktree directories are ignored before adding files.
- Review and approve repository setup and test commands before execution.
Avoid
- Do not create a project-local worktree inside a tracked directory.
- Do not run package installation or tests from an untrusted repository without isolation.
- Do not continue after baseline failures without explicit user approval.