ck:worktree

Create isolated git worktrees for parallel feature development.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/haidonglethqb/CloudSchool --skill ck-worktree-haidonglethqb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:worktree
Source: https://github.com/haidonglethqb/CloudSchool/tree/main/.qwen/skills/worktree
Command: npx skills add https://github.com/haidonglethqb/CloudSchool --skill ck-worktree-haidonglethqb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Hands free parallel feature development by creating isolated git worktrees so work in progress does not interfere with the main working directory.

Core Features & Use Cases

  • Create per-feature worktrees for monorepos and standalone repos, with automatic branch naming based on a chosen prefix.
  • Detect monorepo structures and optionally scope worktrees to specific projects, keeping related worktrees organized.
  • Copy environment templates and explicit env files into new worktrees, ensuring consistent runtime settings.

Quick Start

Run the CLI to create a new worktree for a feature by executing node .claude/skills/worktree/scripts/worktree.cjs create <feature> and supply an optional --prefix and --worktree-root

Frequently Asked Questions about ck:worktree

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

FAQPage Schema
How do I isolate git worktrees for parallel feature development without affecting the main working directory?

To isolate git worktrees for parallel feature development, you create isolated worktrees that allow work in progress to proceed without interfering with the main working directory. This enables hands-free parallel feature branches safely.

How do I create a git worktree for a specific feature in a monorepo?

To create a git worktree for a monorepo feature, run the CLI script with the create command and feature name. The tool detects monorepo structures and optionally scopes worktrees to specific projects, applying prefix-based branch naming automatically.

Can I copy environment templates into new git worktrees to ensure consistent runtime settings?

Yes, you can copy environment templates and explicit env files into new git worktrees. This ensures consistent runtime settings across all isolated work directories created for parallel feature development.

Does creating git worktrees validate potential branch conflicts across worktrees?

Yes, creating git worktrees validates potential branch conflicts across worktrees. Safety checks validate worktree roots, base branches, and potential branch conflicts to prevent naming collisions during parallel feature development.

What is the best way to organize related git worktrees in a monorepo?

The best way to organize related git worktrees in a monorepo is using per-project scoping. The tool detects monorepo structures and scopes worktrees to specific projects, keeping related feature development branches organized.

Can I perform a dry run to validate git worktree creation before applying changes?

Yes, you can perform dry-run validation when creating git worktrees. This safety check validates worktree roots, base branches, and potential branch conflicts across worktrees before actually creating the isolated working directory.