worktree-impl

Create isolated git worktrees under .worktrees/ for implementation projects.

Updated Oct 29, 2013
One-click install
npx skills add https://github.com/whywaita/dotfiles --skill worktree-impl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-impl
Source: https://github.com/whywaita/dotfiles/tree/main/dot_codex/skills/worktree-impl
Command: npx skills add https://github.com/whywaita/dotfiles --skill worktree-impl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a git worktree for isolated implementation after planning. Use when starting implementation or when a clean worktree is requested.

Core Features & Use Cases

  • Create per-feature worktrees under .worktrees/<name> for isolated work.
  • Automatically determine base branch and naming conventions.
  • Manage and delete or reuse worktrees without touching main repo.

Quick Start

Create a new worktree for a feature branch from origin/main and start implementing.

Frequently Asked Questions about worktree-impl

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

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

To create an isolated git worktree, the tool verifies the repository, fetches origin, determines the base branch, and creates a worktree under .worktrees/<sanitized-name> for parallel experimentation.

What is the best way to keep feature development work separate in git?

Using git worktrees keeps feature development separate by creating isolated working directories under .worktrees/<name>, allowing parallel experimentation without touching the main repository state.

Can I reuse or delete a git worktree without affecting the main repository?

Yes, git worktrees created under .worktrees/<name> can be managed, deleted, or reused independently, keeping the main repository clean and untouched during feature development.

Does git worktree creation automatically determine the base branch from origin?

Yes, the process fetches origin and automatically determines the base branch to ensure the new worktree starts from the correct, up-to-date repository state for feature implementation.

When should I use a git worktree instead of a standard branch?

Use a git worktree when you need clean builds or parallel experimentation, as it provides an isolated directory for feature development without switching branches in your main working directory.