Using git worktrees

Skill roronoazoroshao369/vibe-coding-os/skills/core/using-git-worktrees

Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.From the repository description

Install

npx -y skills add roronoazoroshao369/vibe-coding-os --skill using-git-worktrees

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, 318 tokens by cl100k_base, as published. Nobody here has run it

Skill: Using Git Worktrees

Purpose

Isolate risky or parallel work so multiple branches can be developed, tested, or reviewed without corrupting the main checkout.

When to use

Use when work may conflict with current changes, when comparing approaches, when running parallel agent passes, or when a user explicitly requests isolated branch work.

Inputs

Repository status, desired branch name, base branch or commit, current uncommitted changes, and cleanup expectations.

Workflow

Inspect git status and existing worktrees before creating anything.
Choose a descriptive branch and worktree path that reflects the task.
Create the worktree from the correct base without moving or overwriting user changes.
Run implementation and validation inside the isolated worktree.
Keep artifacts, logs, and commits scoped to the worktree branch.
When finished, report the branch, path, validation status, and cleanup recommendation.

Outputs

An isolated branch/worktree ready for focused work, plus a handoff note describing path, base, status, and cleanup steps.

Failure modes

Creating a worktree from the wrong base.
Hiding or overwriting uncommitted user changes.
Forgetting which checkout contains the final patch.
Leaving stale worktrees without a cleanup note.

Verification checklist

git status was inspected first.
Branch and worktree path are named clearly.
No user changes were moved or discarded.
Final report names the active branch/path and cleanup state.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most pr commit review skills give in 318 tokens

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originin 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchin 37 of 1055, across 32 files
Wrap body text at 72 charactersin 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

Choose descriptive branch and worktree path names
Scope artifacts and commits to the worktree branch
Report branch path and validation status upon completion

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.