trycycle-worktrees

Create a Git worktree in .worktrees and run language-aware setup steps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kylesnowschwartz/dotfiles --skill trycycle-worktrees-kylesnowschwartz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trycycle-worktrees
Source: https://github.com/kylesnowschwartz/dotfiles/tree/main/claude/skills/trycycle/subskills/trycycle-worktrees
Command: npx skills add https://github.com/kylesnowschwartz/dotfiles --skill trycycle-worktrees-kylesnowschwartz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This subskill simplifies the process of creating and managing isolated git worktrees, enabling parallel feature development within the same repository while keeping workspaces tidy.

Core Features & Use Cases

  • Create a new worktree at .worktrees/<branch-name> to isolate development.
  • Ensure .worktrees is gitignored to avoid accidental commits to the main workspace.
  • Auto-detect common project setups (Node.js, Rust, Python, Go) and run appropriate setup steps.
  • Report the new worktree path and branch name for quick verification.

Quick Start

Create a new worktree for a feature branch and run the project setup automatically.

Frequently Asked Questions about trycycle-worktrees

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an isolated git worktree for parallel feature development?

The Skill creates an isolated git worktree at .worktrees/<branch-name>, automatically ensuring the directory is gitignored to prevent accidental commits while enabling parallel feature development within the same repository.

Can I automate project setup steps when creating a git worktree for a new branch?

Yes, the Skill auto-detects common project setups including Node.js, Rust, Python, and Go, running language-aware setup steps automatically so your new branch environment is immediately ready for testing or experimentation.

Does git worktree management handle dependencies for Node.js, Rust, Python, and Go projects?

The Skill handles dependencies by auto-detecting Node.js, Rust, Python, and Go project configurations, automatically running the appropriate language-aware setup steps within the newly created isolated worktree path to prepare the environment.

What is the best way to manage multiple git branches without switching contexts in the main workspace?

Using git worktrees is the best way to manage multiple branches without switching contexts, creating isolated directories at .worktrees/<branch-name> for parallel development, testing, or experimentation without disrupting the main repository workspace.

Why should I use a .worktrees directory for git branch management instead of cloning the repository?

Using a .worktrees directory for branch management shares a single repository history, saving disk space and setup time compared to cloning, while the Skill automatically gitignores the path to prevent accidental commits to the main workspace.