git-worktree-setup
Use PROACTIVELY when working on multiple branches simultaneously or creating parallel Claude Code sessions. Automates git worktree creation with prerequisite checking, development environment initialization, and safe cleanup. Supports single worktree, batch creation, and worktree removal. Not for non-git projects or branch management without worktrees.
What this skill does
# Git Worktree Setup Automates git worktree creation for parallel Claude Code sessions without conflicts. ## When to Use **Trigger Phrases**: - "create a worktree for [branch-name]" - "set up worktree for [feature]" - "create worktrees for [branch1], [branch2]" - "remove worktree [name]" - "list my worktrees" **Use Cases**: - Working on multiple features simultaneously - Parallel Claude Code sessions on different branches - Code review while continuing development - Emergency hotfixes without interrupting work ## Quick Decision Matrix | Request | Mode | Action | |---------|------|--------| | "create worktree for X" | Single | Create one worktree | | "set up worktrees for X, Y" | Batch | Create multiple | | "remove worktree X" | Cleanup | Remove specific | | "list worktrees" | List | Display status | ## Workflow Overview ### Phase 0: Prerequisites (Mandatory) ```bash # Verify git repo git rev-parse --is-inside-work-tree # Check uncommitted changes git status --porcelain # Get repo name basename $(git rev-parse --show-toplevel) ``` ### Phase 1: Gather Information - Branch name (required) - New or existing branch - Location (default: `../repo-branch`) - Setup dev environment ### Phase 2: Create Worktree ```bash # New branch git worktree add ../project-feature -b feature # Existing branch git worktree add ../project-bugfix bugfix ``` ### Phase 3: Dev Environment Setup - Detect package manager - Run install - Copy .env files ### Phase 4: Next Steps - Show worktree path - Provide navigation commands - List all worktrees ## Quick Reference Commands ```bash # Create with new branch git worktree add ../project-branch -b branch-name # Create from existing git worktree add ../project-branch branch-name # List all git worktree list # Remove worktree git worktree remove ../project-branch # Remove worktree and branch git worktree remove ../project-branch git branch -D branch-name ``` ## Package Manager Detection | Lock File | Manager | |-----------|---------| | pnpm-lock.yaml | pnpm | | yarn.lock | yarn | | bun.lockb | bun | | package-lock.json | npm | ## Common Issues | Issue | Cause | Fix | |-------|-------|-----| | "invalid reference" | Branch doesn't exist | Use `-b` for new | | "already exists" | Directory exists | Choose different location | | "uncommitted changes" | Dirty working dir | Commit or stash | ## Safety Protocols **Before Creating**: - [ ] Verify git repository - [ ] Check clean working directory - [ ] Validate target directory available **Before Cleanup**: - [ ] Confirm user intent - [ ] Check for uncommitted changes - [ ] Warn about permanent branch deletion ## Example Output ``` ✓ Worktree created: /Users/connor/myapp-feature-auth ✓ Branch: feature-auth (new) ✓ Dependencies installed Next steps: cd ../myapp-feature-auth claude All worktrees: - /path/to/main (main) ← current - /path/to/worktree (feature-auth) ← new ``` ## Success Criteria - [ ] Worktree in correct location - [ ] Branch checked out properly - [ ] Files visible in directory - [ ] Dev environment ready - [ ] Appears in `git worktree list` - [ ] User can start Claude Code ## Reference Materials - `modes/` - Detailed mode workflows - `templates/` - Setup script templates - `data/best-practices.md` - `data/troubleshooting.md` --- **Version**: 1.0.0 | **Author**: Connor
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.