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.

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 888 of the 1,342 authors here whose files we hold, read 2026-08-07

Use conventional commits formatin 127 of 888, across 115 files
Keep subject line under 72 charactersin 62 of 888, across 48 files
Delete branches after mergein 51 of 888, across 38 files
Use imperative mood in subject linein 51 of 888, across 42 files
Use imperative mood in commit messagesin 44 of 888
Verify directory is ignored before creating worktreein 43 of 888, across 12 files
Generate a conventional commit messagein 43 of 888
Add unignored worktree directories to gitignorein 42 of 888, across 10 files
Make atomic commitsin 39 of 888, across 27 files
Run tests before committingin 36 of 888, across 25 files
Verify clean test baselinein 35 of 888, across 9 files
Split unrelated changes into separate commitsin 35 of 888, across 30 files

Said here and by no other author read

choose descriptive branch and worktree paths
create worktree from the correct base
do not move or overwrite user changes
run implementation and validation inside the worktree
keep artifacts scoped to the worktree branch
report branch path status and cleanup recommendation

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.