How do I install the Sk Worktree Safety skill?

Run npx skillmds@latest add gustavo-meilus/sk-worktree-safety in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sk Worktree Safety safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sk Worktree Safety?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sk Worktree Safety free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sk Worktree Safety?

gustavo-meilus (@gustavo-meilus) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sk Worktree Safety by gustavo-meilus

Name: Sk Worktree Safety
Author: gustavo-meilus

Sk Worktree Safety

Enforces a mandatory 4-step safety protocol (Ignore, Setup, Baseline, Commit) for creating, managing, and destroying git worktrees in pipeline isolation contexts. Use when a pipeline step declares `isolation: worktree`, when parallel pattern tasks require branch isolation, or when the iterative or spec-driven patterns require atomic rollback capability.

File contents

Worktree Safety Protocol — Isolated Execution

Defines the mandatory 4-step protocol (Ignore, Setup, Baseline, Commit) for creating, managing, and destroying git worktrees.

The 4-Step Safety Protocol

2. SETUP_AFTER_CREATE

Manifests are auto-detected (package.json, Cargo.toml, etc.) and the corresponding installation commands (npm install, cargo build) are run to prepare the isolated environment.

3. VERIFY_BASELINE

The project's full test suite is run before any modifications.

Failures Found: Results are reported to the user. DO NOT PROCEED with implementation without explicit human authorization.
Goal: Distinguishes between pre-existing issues and pipeline-introduced regressions.

4. COMMIT_BEFORE_DESTROY

All changes are added and committed before any worktree is removed, preserving the work-in-progress state.

cd "$WORKTREE_PATH" && git add -A && git commit -m "wip: pipeline checkpoint"
git worktree remove "$WORKTREE_PATH"

Pattern Integration

Detection Signals

Red Flags — STOP

"I'll skip the baseline test, it'll be fine." → STOP. Pre-existing failures will corrupt the pipeline metrics.
"Just force-remove the worktree, the pipeline failed." → STOP. Commit partial findings first to aid debugging.

Reference Files

sk-pipeline-patterns/SKILL.md — Topology selection.
sk-pipeline-state/SKILL.md — metadata.worktree_root tracking.
finishing-a-development-branch/SKILL.md — Final merge protocol.

---name: sk-worktree-safetydescription: Enforces a mandatory 4-step safety protocol (Ignore, Setup, Baseline, Commit) for creating, managing, and destroying git worktrees in pipeline isolation contexts. Use when a pipeline step declares `isolation: worktree`, when parallel pattern tasks require branch isolation, or when the iterative or spec-driven patterns require atomic rollback capability.---# Worktree Safety Protocol — Isolated Execution> Defines the mandatory 4-step protocol (Ignore, Setup, Baseline, Commit) for creating, managing, and destroying git worktrees.<glossary> <term name="Worktree">An isolated git workspace sharing the same repository object but operating on a different branch and path.</term> <term name="Baseline Verification">Running the project's test suite before modification to identify pre-existing failures.</term> <term name="Atomic Teardown">Committing all uncommitted work before removing the worktree directory.</term></glossary>## The 4-Step Safety Protocol<protocol>### 1. VERIFY_IGNOREDThe `.worktrees/` directory must be git-ignored before any worktree is created, to prevent accidental commits or workspace pollution.```bashgit check-ignore -q .worktrees || { echo ".worktrees/" >> .gitignore && git add .gitignore && git commit -m "chore: ignore worktrees"; }```### 2. SETUP_AFTER_CREATEManifests are auto-detected (`package.json`, `Cargo.toml`, etc.) and the corresponding installation commands (`npm install`, `cargo build`) are run to prepare the isolated environment.### 3. VERIFY_BASELINEThe project's full test suite is run before any modifications.- **Failures Found**: Results are reported to the user. **DO NOT PROCEED** with implementation without explicit human authorization.- **Goal**: Distinguishes between pre-existing issues and pipeline-introduced regressions.### 4. COMMIT_BEFORE_DESTROYAll changes are added and committed before any worktree is removed, preserving the work-in-progress state.```bashcd "$WORKTREE_PATH" && git add -A && git commit -m "wip: pipeline checkpoint"git worktree remove "$WORKTREE_PATH"```</protocol>## Pattern Integration<integration_table>| Pattern | Worktree Requirement | Rationale || :--- | :--- | :--- || **1. Sequential** | Optional | Linear flow may not require isolation. || **2. Parallel** | **Mandatory** | Required for fanned-out task isolation. || **3. Iterative** | **Mandatory** | Enables atomic rollback on escalation. || **4. Gated** | Conditional | Required only during the modification phase. || **5. Spec-Driven** | **Mandatory** | Enforced per-task during Phase 5 (Implement). |</integration_table>## Detection Signals<signals>Environment state is verified before execution:- **`GIT_DIR != GIT_COMMON`**: Already in a linked worktree; Step 1 is skipped.- **Branch empty**: Detached HEAD detected; branching/pushing is not possible. Escalate to user.</signals><invariants>- NEVER skip the baseline test; it is the leading cause of false escalations in iterative loops.- NEVER use `git worktree remove --force` without a preceding commit to preserve findings.- ALWAYS verify that `.worktrees/` is ignored before creation.</invariants>## Red Flags — STOP- "I'll skip the baseline test, it'll be fine." → **STOP**. Pre-existing failures will corrupt the pipeline metrics.- "Just force-remove the worktree, the pipeline failed." → **STOP**. Commit partial findings first to aid debugging.## Reference Files- `sk-pipeline-patterns/SKILL.md` — Topology selection.- `sk-pipeline-state/SKILL.md` — `metadata.worktree_root` tracking.- `finishing-a-development-branch/SKILL.md` — Final merge protocol.

Frequently asked questions