paulnsorensen/worktree
claude/skills/worktree/SKILL.md
Create an isolated git worktree for a Claude Code task, keeping main clean. Use when asked to create or resume a worktree, set up an isolated branch for a task, or when the /worktree command is invoked. Requires a task slug.
$ install --global
skillsauthnpx skillsauth add paulnsorensen/dotfiles 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 27, 2026, 10:12 AM79.5s1 file scanned
SKILL.md
- name:
- worktree
- model:
- haiku
- allowed-tools:
- Bash(ccw-init:*), Bash(cd:*)
- description:
- >
worktree
Create or resume an isolated git worktree for a task.
Protocol
1. Get the slug
The task slug is provided as an argument. If none was given, ask the user for one.
2. Run the helper
ccw-init <slug>
This single command handles everything:
- Validates git repo
- Creates worktree at
.worktrees/<slug>/on branchclaude/<slug>(or resumes if exists) - Symlinks Claude project permissions from main repo
- Disables pre-commit hooks (prek can't write cache inside Seatbelt sandbox)
- Seeds
.claude/settings.local.jsonwith sandbox config + permissions
It outputs JSON to stdout with: path, branch, base_sha, base_branch, created.
3. Confirm
Parse the JSON output and report:
Worktree ready: <path>
Branch: <branch>
Base: <base_sha> (<base_branch>)
Then cd into the worktree path.
What You Don't Do
- Commit, push, or create PRs — use /wt-git for git operations in worktrees
- Set up full project environments — only creates the worktree and seeds settings
- Delete worktrees — use /worktree-sweep for cleanup
Gotchas
- Worktree creation fails if the branch already exists on remote — use a unique branch name
- Worktree path must not contain spaces — use slugified names only
Related Skills
paulnsorensen/work-recovery
tools
VerifiedTrustedCommunity
Reconstruct what a past coding-agent session was doing so you can resume it — goal, files touched, last verified state, and the next step — by querying the session logs. Use when the user says "what was I working on", "recover that session", "reconstruct where I left off", "resume my last session", "what did that session change", "rebuild context from logs", or invokes /work-recovery. Report-only — it never scores or judges. Do NOT use for usage scoring (that is /skill-improver, /tool-efficiency, /prompt-analytics) or one-off interactive log queries (that is /session-analytics).
2SKILL.mdUpdated Jun 3, 2026
paulnsorensen/wiki-curator
development
VerifiedTrustedCommunity
Curate this repo's hallouminate wiki (.hallouminate/wiki/, the repo:dotfiles:wiki corpus) — add or update architecture pages, per-harness docs, and gotchas. Use when the user says "update the wiki", "document this in the wiki", "refresh the harness docs", "add a wiki page", "curate the wiki", "the wiki is stale", or invokes /wiki-curator. Also use at session end to write back a non-obvious decision or gotcha worth preserving. Grounds the existing wiki first, follows one-topic-per-file conventions, verifies every external doc URL before writing, and reindexes. Do NOT use for general code search (that is cheez-search) or for editing AGENTS.md command reference.
2SKILL.mdUpdated Jun 3, 2026
paulnsorensen/tool-efficiency
tools
VerifiedTrustedCommunity
Audit how a tool, command, or MCP server is actually used across coding-agent sessions and produce calibrated recommendations — tool-vs-task fit, error forensics, fix recommendations, permission friction, MCP health, and token economics. Use when the user says "tool efficiency", "am I using X efficiently", "audit tool usage", "why does X keep failing", "how do I fix this error", "what should I change", "permission friction", "is this MCP worth it", "tool error rate", "fix recommendations", or invokes /tool-efficiency. Do NOT use for auditing a skill or agent definition (that is /skill-improver) or for one-off interactive log queries (that is /session-analytics).
2SKILL.mdUpdated Jun 3, 2026
paulnsorensen/prompt-analytics
tools
VerifiedTrustedCommunity
Analyze how prompts and skill routing behave across coding-agent sessions and produce calibrated recommendations — prompt-pattern analysis, routing accuracy, and knowledge gaps. Use when the user says "analyze my prompts", "prompt patterns", "is routing working", "which skill should have fired", "knowledge gaps", "what do I keep asking", or invokes /prompt-analytics. Do NOT use for auditing a single skill/agent definition (that is /skill-improver), tool/MCP efficiency (that is /tool-efficiency), or one-off interactive log queries (that is /session-analytics).
2SKILL.mdUpdated Jun 3, 2026