he-worktree

Create and validate isolated Git worktrees or branches for task execution.

4|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/mattjefferson/harness-engineering --skill he-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: he-worktree
Source: https://github.com/mattjefferson/harness-engineering/tree/main/skills/he-worktree
Command: npx skills add https://github.com/mattjefferson/harness-engineering --skill he-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that your work on a Git repository is isolated in a safe, dedicated workspace, preventing conflicts with ongoing human changes and maintaining a clean development environment.

Core Features & Use Cases

  • Workspace Isolation: Creates separate Git worktrees or branches for specific tasks.
  • Conflict Prevention: Avoids collisions between automated tasks and manual development.
  • Use Case: Before starting a complex feature implementation, use this Skill to create a dedicated worktree, ensuring your development doesn't interfere with the main branch or other team members' work.

Quick Start

Use the he-worktree skill to create a new isolated workspace for the 'feature-x' initiative.

Frequently Asked Questions about he-worktree

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

FAQPage Schema
How do I isolate my git workspace to prevent conflicts during automated tasks?

To isolate a git workspace safely, you can create a dedicated Git worktree or branch. This prevents collisions between automated harness workflows and ongoing manual development changes by maintaining a separate working directory.

What is the best way to create an isolated git branch for feature development?

Creating an isolated git branch involves detecting your current repository state and selecting a safe workspace creation strategy. This approach manages branch naming conventions automatically and provides explicit workspace details for downstream tasks.

When do I need to use a git worktree instead of a standard branch?

You need a git worktree when you require a separate working directory linked to the same repository to prevent conflicts. It is ideal for isolating complex feature implementations from the main branch without interfering with team members.

Does this workspace isolation approach validate the git workspace after creation?

Yes, the workspace creation process includes explicit verification steps. After detecting the current state and selecting a worktree or branch strategy, it validates the new isolated workspace to ensure safe execution for downstream tasks.

How do I manage branch naming conventions for isolated development workflows?

Managing branch naming conventions is handled automatically during the workspace creation process. The strategy selects appropriate naming patterns when generating your isolated git worktree or branch to ensure clear tracking and safe integration.