Skip to content
Skills Library
Programming · Automation

isolate

/isolate

Use when starting feature work that needs isolation from current workspace or before executing implementation plans — creates isolated git worktrees with smart directory selection and safety verification

Repository
techneering ↗
Licence
MIT
Last repository change
23.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when starting feature work that needs isolation from current workspace or before executing implementation plans — creates isolated git worktrees with smart directory selection and safety verification

Original author description

Use when starting feature work that needs isolation from current workspace or before executing implementation plans — creates isolated git worktrees with smart directory selection and safety verification

How it works

  1. Core Principle
  2. Steps
  3. Red Flags
  4. Quick Reference
  5. Next Step
  6. Guardrails
Original SKILL.md headings · 92 lines, 472 words
SKILL.md preview
---
name: isolate
description: Use when starting feature work that needs isolation from current workspace or before executing implementation plans — creates isolated git worktrees with smart directory selection and safety verification
---

# Using Git Worktrees

Create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching.

## Core Principle

```
SYSTEMATIC DIRECTORY SELECTION + SAFETY VERIFICATION = RELIABLE ISOLATION.
Never create a worktree without verifying it's gitignored.
```

## Steps

### Step 1: Directory Selection

Follow this priority order:

1. **Check existing directories:**
   ```bash
   ls -d .worktrees 2>/dev/null     # Preferred (hidden)
   ls -d worktrees 2>/dev/null      # Alternative
   ```
   If found: Use that directory. `.worktrees` wins if both exist.

2. **Check CLAUDE.md:**
   ```bash
   grep -i "worktree.*director" CLAUDE.md 2>/dev/null
   ```
   If preference specified: Use it without asking.

3. **Ask user** (only if no directory exists and no preference):
   ```
   No worktree directory found. Where should I create worktrees?
   1. .worktrees/ (project-local, hidden)
   2. ~/.config/tn/worktrees/<project-name>/ (global location)
   ```

### Step 2: Safety Verification

**MUST verify directory is ignored before creating worktree:**

```bash
git check-ignore -q .worktrees 2>/dev/null
```

**If NOT ignored:** Add to .gitignore and commit.

### Step 3: Create Worktree

1. Detect project name: `project=$(basename "$(git rev-parse --show-toplevel)")`
2. Create worktree: `git worktree add "$path" -b "$BRANCH_NAME"`
3. Run project setup (auto-detect from package.json, Cargo.toml, etc.)
4. Verify clean baseline (run tests)
5. Record the baseline state (passing test count / suite output) so later `tn:gate` or `tn:audit` can compare against it
6. Report location

**If no test command exists:** degrade gracefully — record "no tests; baseline = clean checkout + setup completes" and note it in the report. Do not block isolation on a project that legitimately has no tests.

## Red Flags

| Thought | Reality |
|---------|---------|
| "Directory doesn't need gitignore" | Unignored worktrees pollute version control |
| "Skip baseline tests, just start" | Baseline test failure means environment issues — must resolve first |
| "Develop directly on the current branch" | Unisolated development pollutes the main branch |
| "Worktree is done once created" | Must verify the test baseline passes before starting work |

## Quick Reference

| Dimension | Key point |
|-----------|-----------|
| Directory priority | .worktrees → worktrees → CLAUDE.md → ask user |
| Safety check | Must verify gitignore |
| Baseline verification | Run tests after creation to ensure clean |
| Cleanup | Handled by tn:ship |

## Next Step

When done:
- Normal case → return to caller (usually `tn:assemble` or `tn:forge`), continue implementation flow
- Baseline tests fail → report failure reason, ask user whether to continue
- User requests stop → end the current flow

## Guardrails

- Never create a worktree without verifying the directory is gitignored
- If baseline tests fail, report and ask — don't proceed silently
- Follow existing directory conventions if they exist
- Announce at start: "I'm using the tn:isolate skill to set up an isolated workspace."
- Pairs with `tn:ship` for cleanup after work is complete

Versions

The database has no other skills named isolate.

Database snapshot: 13.11.2026 · package version e9cbc9997878 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100git-worktrees
    Use when starting feature work that needs isolation from current workspace, before executing implementation plans, or when MORE THAN ONE SESSION is working on one checkout - creates isolated git worktrees with smart directory selection and safety verification
  • 100using-git-worktrees
    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
  • 100using-git-worktrees
    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
  • 100using-git-worktrees
    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
  • 100using-git-worktrees
    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
  • 100using-git-worktrees
    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.