# Loom Workspace

> Use loom workspace to create/manage worktrees for isolated execution of tickets.

- Skill: `majiayu000/loom-workspace` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/loom-workspace`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/loom-workspace/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/loom-workspace

---


<!-- BEGIN:compound:skill-managed -->
## 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.
<!-- END:compound:skill-managed -->

## Manual notes

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