loom-workspace — how to use loom-workspace how to use loom-workspace, loom-workspace alternative, loom-workspace setup guide, what is loom-workspace, loom-workspace vs git, loom-workspace install, loom-workspace worktree management, terminal interface management, TUI management tool

Worktree basics (repo model)

Ensure a worktree exists for a branch:

• compound_workspace(argv=["repo", "worktree", "add", "<branch>"])

List worktrees:

• compound_workspace(argv=["repo", "worktree", "ls"])

Remove a worktree:

• compound_workspace(argv=["repo", "worktree", "rm", "<branch>"])

Repo status:

• compound_workspace(argv=["repo", "status"])

Branch naming

Recommended:

• ticket-<ticket-id>-<short-slug>

Example:

• ticket-42-streaming-chunking

Practical note

OpenCode runs inside one working directory. Typically, this is the main branch worktree. loom workspace creates the worktree path (usually under .loom-repo/worktrees/<branch>). Do the code changes in that worktree.

Manual notes

This section is preserved when the skill is updated. Put human notes, caveats, and exceptions here.