workforest

This skill should be used when the user asks about 'workforest', 'git forest', 'git forest list', 'git forest add', 'git forest remove', 'forest layout', or mentions managing worktrees with workforest. Also use when the user asks how workforest works, how to use git forest commands, or how to navigate a forest.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/git-workforest/skills/workforest/SKILL.md

Working with git-workforest

Name: workforest
Rating: 62.4 (1 reviews)
Author: dwmkerr

git-workforest manages git worktrees with a simple, predictable folder structure. Like git worktree, but handles paths for you. Each branch gets its own directory.

Detecting a forest

A directory is a forest if it contains a .workforest.yaml marker file. Trees (worktrees) are subdirectories that are git checkouts.

Commands

Command	Purpose	Git worktree equivalent
`git forest list`	List all trees in the forest	`git worktree list`
`git forest add <branch>`	Add a tree for a branch	`git worktree add <path> <branch>`
`git forest remove <branch>`	Remove a tree from the forest	`git worktree remove <path>`
`git forest remove -f <branch>`	Force remove (even if dirty)	`git worktree remove --force <path>`
`git forest clone <org/repo>`	Clone into structured forest path	`git clone`
`git forest migrate`	Convert existing repo to forest layout	-
`git forest init`	Detect context and set up a forest	-

Forest layout

The forest root is the top-level directory containing .workforest.yaml. It is NOT a git repo itself — each tree inside it is an independent git checkout. All git forest commands can run from any tree or the forest root; workforest walks up to find .workforest.yaml automatically.

~/repos/github/dwmkerr/effective-shell/   # forest root
  .workforest.yaml                         # marks this as a forest
  main/                                    # default branch (primary clone)
  feat/
    dark-mode/                             # worktree or fat clone
    sessions-view/
  fix/
    login-bug/

List output conventions

git forest list mirrors git branch -l colours:

on branch feat/dark-mode in org/repo

trees:
  main            ./main
+ docs/readme     ./docs/readme
* feat/dark-mode  ./feat/dark-mode
+ fix/login-bug   ./fix/login-bug

* (green) - active tree (cwd is inside it)
+ (cyan) - worktree branch
blank - default branch when not active
Paths are bright white with ./ prefix
Default branch sorts first, rest alphabetical

Working in a forest

Each tree is an independent working directory - no stashing needed to switch branches
cd between trees to switch context
Run git forest list from any tree or the forest root to see all branches
The forest root is the parent of all trees, identified by .workforest.yaml

Adding and removing trees

All commands run from inside a tree (e.g. ~/repos/github/dwmkerr/effective-shell/main/). The forest root is the parent directory containing .workforest.yaml — workforest resolves it automatically. New trees are created as siblings of your current tree:

# pwd: ~/repos/github/dwmkerr/effective-shell/main/

git forest add feat/new-feature
# creates ~/repos/github/dwmkerr/effective-shell/feat/new-feature/
# prints: cd ../feat/new-feature

git forest add fix/bug-123
# creates ~/repos/github/dwmkerr/effective-shell/fix/bug-123/

git forest remove fix/bug-123      # removes the tree (refuses if dirty)
git forest remove -f fix/bug-123   # force remove even with uncommitted changes

Trees are created as git worktrees by default, or as full clones if fatTrees: true is set in ~/.workforest.yaml.

When helping users in a forest

If the user is in a forest, use git forest list to understand the layout
When suggesting branch operations, prefer git forest add over git checkout
After add, remind the user to cd to the new tree directory
The forest root is NOT a git repo - individual trees are

Repository: dwmkerr/git-workforest
Path: plugins/git-workforest/skills/workforest/SKILL.md
Commit: 4b08fab

Last updated: 4 days ago
First committed: 5 months ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.