sp-worktree

Create isolated git worktrees on new branches for feature development.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/JZKK720/cubecloud-agentic-os --skill sp-worktree-jzkk720
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sp-worktree
Source: https://github.com/JZKK720/cubecloud-agentic-os/tree/main/.agents/skills/sp-worktree
Command: npx skills add https://github.com/JZKK720/cubecloud-agentic-os --skill sp-worktree-jzkk720

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill creates isolated git worktrees on new branches to ensure the main branch remains clean and maintainable during feature development.

Core Features & Use Cases

  • Isolated Worktrees: Creates a separate worktree for each feature, protecting the main branch from potential issues.
  • Baseline Verification: Ensures a clean test baseline before starting implementation, preventing broken states.
  • Branch Naming Conventions: Standardizes branch naming to maintain readability and consistency.
  • Worktree Hygiene: Provides guidelines for maintaining and cleaning up worktrees after feature completion.
  • Use Case: When starting a new feature, create a worktree with git worktree add <repo>-<feature> -b feat/<feature-slug> to ensure that the main branch remains clean and ready for deployment.

Quick Start

Create an isolated worktree for your feature 'new-UI' with git worktree add -b feat/new-ui <repo>.

Frequently Asked Questions about sp-worktree

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

FAQPage Schema
How do I use git worktrees to keep my main branch clean during feature development?

Use git worktrees to isolate feature changes on separate branches, ensuring the main branch remains clean and ready for deployment. Create a worktree with `git worktree add -b feat/feature-slug` to protect your baseline from potential issues.

What is the best way to manage parallel feature work without breaking the main codebase?

Managing parallel feature work is best achieved by creating isolated git worktrees for each branch. This approach standardizes branch naming conventions and maintains code hygiene by preventing broken states from affecting your main codebase.

How do I create a separate git worktree for a new feature branch?

To create a separate git worktree for a new feature, run `git worktree add <repo>-<feature> -b feat/<feature-slug>`. This isolates your new feature branch, protecting the main branch from potential issues during development.

Do I need to verify a clean test baseline before starting feature development with git worktrees?

Yes, verifying a clean test baseline before starting implementation prevents broken states in your isolated worktrees. This baseline verification step ensures your feature development begins from a stable and maintainable codebase.

How should I handle worktree cleanup and hygiene after feature completion?

Worktree hygiene requires cleaning up isolated worktrees after feature completion to maintain a readable and consistent repository. Standardizing branch naming conventions and removing completed worktrees prevents clutter and maintains codebase integrity.