tmchow/git-worktree
plugins/iterative-engineering/skills/git-worktree/SKILL.md
Internal skill for workspace isolation. Detects current git state and offers worktree/branch options. Called by iterative:implementing, not user-invocable.
$ install --global
skillsauthnpx skillsauth add tmchow/tmc-marketplace 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 17, 2026, 2:30 AM8.9s1 file scanned
SKILL.md
- name:
- git-worktree
- description:
- Internal skill for workspace isolation. Detects current git state and offers worktree/branch options. Called by iterative:implementing, not user-invocable.
- user-invocable:
- false
Git Worktree (Workspace Isolation)
Ensures agent has an isolated workspace to avoid conflicts with human work.
When Called
- At the start of
iterative:implementingskill - At the start of feature work requiring isolation from the current branch
- When workspace isolation is needed
- Not directly invocable by users
Workflow
- Sync with remote. Pull latest from default branch.
- Detect current state. Check if in worktree (
git rev-parse --git-dircontains/worktrees/), get current branch (git branch --show-current), get default branch (git remote show origin | grep "HEAD branch"). - Choose workspace based on current state:
- Already in worktree: confirm it's for this feature, then proceed
- On default branch: ask the user — A) Create worktree (recommended), B) Create branch, C) Continue on main (requires explicit consent)
- On feature branch: ask the user — A) Continue on this branch, B) Create new worktree
- Execute choice. If worktree:
git worktree add ../[repo]-[branch] -b [branch]. If new branch:git checkout -b [branch-name]. If continue: proceed. - Verify. Report: "Ready on branch [name] in [directory]"
Worktree Creation
When creating a worktree:
- Generate branch name from feature/task context
- Create worktree:
git worktree add ../[repo]-[branch] -b [branch] - Copy necessary files (.env, etc.) if they exist
- Verify worktree is functional
Output
Returns to calling skill:
- Branch name
- Directory path (if worktree created)
- Isolation status confirmed
Related Skills
tmchow/iterative:tech-planning
testing
VerifiedTrustedCommunity
Turn requirements into a structured implementation plan with subtasks, dependencies, file paths, and test scenarios. Triggers: "create a plan", "tech planning", "write a tech plan", or has requirements ready to formalize.
21SKILL.mdUpdated Apr 17, 2026
tmchow/iterative:research
data-ai
VerifiedTrustedCommunity
Investigate open questions through parallel research — prior art, constraints, competitive analysis. Triggers: "research this", "investigate questions", "resolve open questions", "look into this", or when a PRD has unresolved questions.
21SKILL.mdUpdated Apr 17, 2026
tmchow/plan-review
development
VerifiedTrustedCommunity
Review PRDs, brainstorm docs, tech plans, design docs, specs, or any planning document for issues. This skill should be used whenever the user wants feedback, critique, or a quality check on an existing planning or requirements document — even if they don't use the word "review." Common triggers include: "review the plan", "check the PRD", "critique my tech plan", "what's wrong with this plan", "poke holes in the requirements", "is this plan solid", "take a look at this spec", "give feedback on the brainstorm", or pointing to a doc file and asking if anything is off. Also triggers after writing a PRD or tech plan (to review what was just created), or when invoked by brainstorming or tech-planning skills. Do NOT trigger for code review (PRs, diffs, source files), writing/creating new plans, debugging, or reviewing non-planning documents (READMEs, CLAUDE.md, test coverage).
21SKILL.mdUpdated Apr 17, 2026
tmchow/iterative:implementing
development
VerifiedTrustedCommunity
Execute a tech plan with dependency-aware batching, TDD, code review, and PR creation. Triggers: "implement the plan", "start building", "start implementing", "execute the plan".
21SKILL.mdUpdated Apr 17, 2026