Claude-skill-registry-data loom-workspace

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

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry-data

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry-data "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/loom-workspace" ~/.claude/skills/majiayu000-claude-skill-registry-data-loom-workspace && rm -rf "$T"

manifest: data/loom-workspace/SKILL.md

source content

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.