worker-git-worktree

Create isolated git worktrees with enforced branch naming and pinned base commits.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AmirTlinov/magray-marketplace --skill worker-git-worktree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worker-git-worktree
Source: https://github.com/AmirTlinov/magray-marketplace/tree/main/flagship-team/skills/worker-git-worktree
Command: npx skills add https://github.com/AmirTlinov/magray-marketplace --skill worker-git-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a secure and isolated environment for developers to perform git operations, preventing accidental modifications to the main codebase and ensuring adherence to specific branching and commit strategies.

Core Features & Use Cases

  • Worktree Isolation: Ensures all development and git operations are confined to a separate worktree.
  • Branch Naming Convention: Enforces a standardized branch naming format (worker/<issue-number>-<short-slug>).
  • Base SHA Pinning: Locks development to a specific base commit SHA for consistency.
  • Recovery Mechanisms: Provides clear steps for recovering from accidental work outside the worktree or dealing with a broken worktree.
  • Use Case: A developer needs to implement a new feature tied to a specific issue. This Skill ensures their work is isolated, branches correctly, and is based on the designated commit, preventing conflicts and maintaining a clean history.

Quick Start

Create a new git worktree for issue 123 with slug feature-x based on commit abc1234.

Frequently Asked Questions about worker-git-worktree

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

FAQPage Schema
How do I use git worktree for isolated development on a specific commit?▼

Git worktree isolation confines development to a separate worktree by enforcing branch naming conventions and pinning a base commit SHA. This prevents accidental modifications to the main codebase and maintains a clean history.

What is the required branch naming convention for isolated git worktrees?▼

Branch naming conventions for isolated git worktrees require a standardized format of worker/<issue-number>-<short-slug>. This enforces project-specific git workflows and ensures strict separation of development tasks tied to designated issues.

Do I need git command-line tools to create and manage isolated worktrees?▼

Git command-line tools are required for worktree creation and management. This Skill manages isolated git worktree environments by leveraging command-line operations to enforce branch naming and base commit pinning for safe development.

How do I recover from accidental modifications made outside the git worktree?▼

Recovery from accidental work outside the git worktree involves following clear, structured recovery mechanisms provided by the isolation workflow. These steps guide developers back to a safe state, ensuring development remains confined to the correct separate worktree.

What's the best way to lock development to a specific base commit in git?▼

Base SHA pinning locks development to a specific base commit SHA for consistency. This mechanism ensures isolated worktrees start from a designated point, preventing conflicts and maintaining a clean project history across separate development tasks.

Why does strict branch isolation matter when implementing features tied to issues?▼

Strict branch isolation prevents accidental modifications to the main codebase during feature implementation. It ensures adherence to specific branching and commit strategies, preventing conflicts and maintaining a clean history for issue-based development.