---

name: ck:worktree description: "Create isolated git worktree for parallel development in monorepos." argument-hint: "[feature-description] OR [project] [feature]"

Git Worktree

Create an isolated git worktree for parallel feature development.

Workflow

Step 1: Get Repo Info

node .opencode/skills/worktree/scripts/worktree.cjs info --json

Parse JSON response for: repoType, baseBranch, projects, worktreeRoot, worktreeRootSource.

Step 2: Detect Branch Prefix

From user's description:

• "fix", "bug", "error", "issue" → fix
• "refactor", "restructure", "rewrite" → refactor
• "docs", "documentation", "readme" → docs
• "test", "spec", "coverage" → test
• "chore", "cleanup", "deps" → chore
• "perf", "performance", "optimize" → perf
• Default → feat

Step 3: Convert to Slug

"add authentication system" → add-auth "fix login bug" → login-bug Max 50 chars, kebab-case.

Step 4: Handle Monorepo

If repoType === "monorepo" and project not specified, use AskUserQuestion:

AskUserQuestion({
  questions: [{
    header: "Project",
    question: "Which project for the worktree?",
    options: projects.map(p => ({ label: p.name, description: p.path })),
    multiSelect: false
  }]
})

Step 5: Execute

Monorepo:

node .opencode/skills/worktree/scripts/worktree.cjs create "<PROJECT>" "<SLUG>" --prefix <TYPE>

Standalone:

node .opencode/skills/worktree/scripts/worktree.cjs create "<SLUG>" --prefix <TYPE>

Options:

• --prefix - Branch type: feat|fix|refactor|docs|test|chore|perf
• --worktree-root <path> - Override default location (only if needed)
• --json - JSON output
• --dry-run - Preview

Step 6: Install Dependencies

Based on project context, run in background:

• bun.lock → bun install
• pnpm-lock.yaml → pnpm install
• yarn.lock → yarn install
• package-lock.json → npm install
• poetry.lock → poetry install
• requirements.txt → pip install -r requirements.txt
• Cargo.toml → cargo build
• go.mod → go mod download

Commands

Command	Usage	Description
create	create [project] <feature>	Create worktree
remove	remove <name-or-path>	Remove worktree
info	info	Repo info with worktree location
list	list	List worktrees

Notes

• Script auto-detects superproject, monorepo, and standalone repos
• Default worktree location is smart: superproject > monorepo > sibling
• Use --worktree-root only to override defaults
• Env templates (.env*.example) auto-copied with .example suffix removed

Claude Skill Registry (Data)

This repo contains the archived skill contents (the heavy, browsable skill files).

Canonical layout

• Category folders at repo root (e.g. development/, documents/, data/, ...)
• Each skill lives under a category: <category>/<skill>/SKILL.md + <category>/<skill>/metadata.json
• Case conflicts are resolved with {name}-{owner}-{repo} suffixes (fallback: -{short-hash}).

Archive status

• Live badges above are sourced from claude-skill-registry-core stats.json.
• Counts in this README are intentionally dynamic, not hardcoded.
• If the badges look stale, refresh the core build/index pipeline rather than editing numbers here.

Where the index + site live

• Core repo: https://github.com/majiayu000/claude-skill-registry-core
• Main repo (merged publish artifact): https://github.com/majiayu000/claude-skill-registry