outthislife/brooklyn-skills · Archived

work

>- Kick off a task in a fresh isolated git worktree instead of the current checkout. Use when the user invokes /work (optionally with a slug or description) to start something new without touching their working tree.

First seen Aug 10, 2026

Installation

$ npx skills add outthislife/brooklyn-skills --skill work

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from outthislife/brooklyn-skills · top by installs.

npx skills add outthislife/brooklyn-skills

Browse all from outthislife/brooklyn-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 185
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,264 B
  • docs SUMMARY.md 225 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 6 installs

SKILL.md

/work

/work [slug] is a declaration for this task: "spin up a dedicated worktree and do the work there." It applies to what the user is starting right now — it is not a standing rule that all work always happens in worktrees.

When invoked:

  1. Look at what the repo already does, and copy it.
  2. Create the worktree + branch and cd into it.
  3. Do the requested work there.

Read the repo's conventions

git worktree list                                   # sibling dirs + branches
git branch -a --sort=-committerdate | head -20      # branch prefix/slug pattern
git remote show origin | sed -n 's/.*HEAD branch: //p'   # default branch
  • Branch prefix — mirror the dominant one (e.g. <initials>/<slug>). None

obvious → ask.

  • Worktree dir — mirror sibling naming/location (commonly <repo>-<short>

next to the primary checkout). Short suffix ≠ full branch is fine.

  • Base — current default branch unless they name another.
  • Slug — from the /work argument, else the task description.

Create it

repo="$(git rev-parse --show-toplevel)"
parent="$(dirname "$repo")"
default="$(git -C "$repo" remote show origin | sed -n 's/.*HEAD branch: //p')"
git -C "$repo" fetch origin "$default"
git -C "$repo" worktree add -b <prefix>/<slug> "$parent/$(basename "$repo")-<short>" "origin/$default"
cd "$parent/$(basename "$repo")-<short>"

Reuse a matching worktree/branch if one already exists — don't duplicate. Match how siblings handle node_modules / .venv / symlinks.

Then

  • Do the task in the worktree; never in the primary checkout, and never in

another agent's worktree.

  • UI → ui-only + ui-system. Tests → whatever the repo uses.
  • When handing off, tell the user the worktree path and how to run it.
  • Ship → commit, push the branch, open a PR/MR to the default branch.
  • Cleaning up → offer to remove worktrees whose branch is already merged.
  • Reviewing an existing PR instead of new work → pr-triage.