harness-worktree

Create an isolated git worktree for Harness implementation work.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill harness-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-worktree
Source: https://github.com/Refinex-Space/Refinex-Skills/tree/main/plugins/harness-powers/skills/harness-worktree
Command: npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill harness-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create an isolated workspace for Harness implementation work to prevent unintended changes on main branches and ensure a clean baseline before executing plans.

Core Features & Use Cases

  • Provides a dedicated git worktree for feature or fix work
  • Prevents plan execution on main/master unless explicitly allowed
  • Performs setup and baseline checks to establish a known starting state

Quick Start

Create an isolated worktree, verify the repository's ignored directories, run setup and baseline checks, and prevent plan execution on main unless explicitly allowed.

Frequently Asked Questions about harness-worktree

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

FAQPage Schema
How do I isolate feature work from the main branch using git worktree?

Git worktree isolation creates a dedicated workspace for feature or fix work, preventing unintended changes on main branches by establishing a clean baseline before executing plans.

Can I execute implementation plans directly on the main branch?

Plan execution is blocked on main or master branches unless explicitly allowed, enforcing isolation by requiring a dedicated worktree to prevent unintended changes to the baseline.

What setup checks are needed before starting work in a git worktree?

Before starting work, setup and baseline checks verify the repository's ignored directories and establish a known starting state, ensuring a clean codex-style worktree is prepared for feature implementation.

Why should I use a git worktree for devops branching workflows?

Git worktree provides safe isolation for devops workflows by creating a dedicated workspace that prevents unintended changes on main branches and ensures a clean baseline before executing implementation plans.

Does this worktree approach require any specific dependencies?

No specific dependencies are required to create an isolated git worktree workspace, allowing you to prevent unintended changes on main branches and verify ignored directories without additional tooling.

What's the best way to prevent accidental commits to main during feature development?

The best way is using an isolated git worktree that blocks plan execution on main unless explicitly allowed, performing setup and baseline checks to establish a safe starting state for feature work.