git-worktree-setup

Create isolated Git worktrees with prefixed branches and copied environment files.

3|1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/andres-vv/Flowkify-mission-10x --skill git-worktree-setup-andres-vv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-worktree-setup
Source: https://github.com/andres-vv/Flowkify-mission-10x/tree/main/skills/git-worktree-setup
Command: npx skills add https://github.com/andres-vv/Flowkify-mission-10x --skill git-worktree-setup-andres-vv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation of isolated development environments using Git worktrees, preventing conflicts and allowing parallel feature development without disrupting ongoing work.

Core Features & Use Cases

  • Parallel Development: Easily start new features, bug fixes, or quality-of-life improvements in separate, clean worktrees.
  • Branch Management: Automatically creates branches with appropriate prefixes (feature, bugfix, qol) and integrates ticket numbers when available.
  • Environment Consistency: Copies .env and .cursor/mcp.json to new worktrees, ensuring consistent environment variables and configurations.
  • Use Case: When asked to "start working on the new login flow without touching the current dashboard work", this skill will set up a dedicated worktree for the login flow.

Quick Start

Use the git worktree setup skill to create a new feature branch for ticket 1234 with the short description 'user-profile-page'.

Frequently Asked Questions about git-worktree-setup

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

FAQPage Schema
How do I set up an isolated Git worktree for parallel feature development?

To set up an isolated Git worktree, you create a separate directory linked to a new branch, which allows parallel feature development without disrupting ongoing work in your main repository.

Can I automatically copy .env files when creating a new Git worktree?

Yes, you can automatically copy .env files when creating a new Git worktree to ensure environment consistency. This process duplicates your environment variables and configurations into the new working directory.

How do I create Git branches with prefixes like feature or bugfix using worktrees?

You can create Git branches with prefixes like feature or bugfix by integrating ticket numbers into the worktree creation process, automatically generating appropriately named branches for specific tasks.

Does setting up a Git worktree run npm install and prisma generate automatically?

Yes, setting up a Git worktree can run npm install and prisma generate automatically. This ensures your new isolated development environment has all dependencies installed and database clients generated immediately.

What is the best way to work on a new feature without touching my current Git branch?

The best way to work on a new feature without touching your current Git branch is creating an isolated worktree. This sets up a dedicated directory for your new task while keeping your existing work completely undisturbed.

Can I integrate ADO ticket numbers when creating a Git worktree?

Yes, you can integrate ADO ticket numbers when creating a Git worktree. The worktree setup process supports incorporating ticket numbers from systems like ADO directly into your branch naming conventions.