Adoption

Agent Skills are supported by leading AI development tools.

VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory

oaknational/worktrees

Name: worktrees
Author: oaknational

.agent/skills/worktrees/SKILL.md

npx skillsauth add oaknational/oak-open-curriculum-ecosystem worktrees

Clean

TrivyContainer and dependency vulnerability scanner

Clean

SemgrepStatic code analysis for vulnerabilities

Clean

mcp-scan (Snyk)Model Context Protocol security validation

Skipped

Snyk (dep)Open source security scanning

Skipped

Socket.devSupply chain security analysis

Skipped

VirusTotalMulti-engine malware detection

Skipped

CrowdStrikeAdvanced threat intelligence

Skipped

OSV-ScannerOpen Source Vulnerability database check

Skipped

OWASP Dep-Check

Git Worktrees

Guidance on using git worktrees to isolate work without disrupting the main checkout.

When to Use

Parallel feature work: developing two features simultaneously without branch switching
Risky experiments: trying an approach that might need to be discarded entirely
Review isolation: checking out a PR branch for review without losing your current state
Plan execution: executing an implementation plan in isolation (recommended by execution skills)

How to Use

Create a worktree

git worktree add .claude/worktrees/<name> -b <branch-name>

Or use the platform's worktree support (e.g., Claude Code's EnterWorktree tool).

Work in the worktree

The worktree is a full checkout with its own working directory
Changes in the worktree do not affect the main checkout
Both checkouts share the same .git directory (commits are visible from both)

Clean up

git worktree remove .claude/worktrees/<name>

Remove worktrees when the work is complete and merged. Stale worktrees consume disk space.

Conventions

Worktrees live under .claude/worktrees/ (gitignored)
Name worktrees descriptively: feature-auth, fix-search-bug, review-pr-42
Do not leave worktrees open indefinitely — clean up after merge

References

git worktree documentation: git help worktree

oaknational/worktrees

.agent/skills/worktrees/SKILL.md

When and how to use git worktrees for isolated work. Use for parallel development, risky experiments, or review work that should not affect the main working directory.

3 stars

development

Updated Apr 15, 2026

$ install --global

skillsauth

npx skillsauth add oaknational/oak-open-curriculum-ecosystem worktrees

Install 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.

Scanners Passed

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 15, 2026, 9:51 PM7.5s1 file scanned

SKILL.md

name:: worktrees
classification:: passive
description:: >-

Git Worktrees

Guidance on using git worktrees to isolate work without disrupting the main checkout.

When to Use

Parallel feature work: developing two features simultaneously without branch switching
Risky experiments: trying an approach that might need to be discarded entirely
Review isolation: checking out a PR branch for review without losing your current state
Plan execution: executing an implementation plan in isolation (recommended by execution skills)

How to Use

Create a worktree

git worktree add .claude/worktrees/<name> -b <branch-name>

Or use the platform's worktree support (e.g., Claude Code's EnterWorktree tool).

Work in the worktree

The worktree is a full checkout with its own working directory
Changes in the worktree do not affect the main checkout
Both checkouts share the same .git directory (commits are visible from both)

Clean up

git worktree remove .claude/worktrees/<name>

Remove worktrees when the work is complete and merged. Stale worktrees consume disk space.

Conventions

Worktrees live under .claude/worktrees/ (gitignored)
Name worktrees descriptively: feature-auth, fix-search-bug, review-pr-42
Do not leave worktrees open indefinitely — clean up after merge

References

git worktree documentation: git help worktree

Related Skills