From loom
Coordinate Git isolation and provenance for Loom work. Use when branches, worktrees, baselines, diffs, merges, or PR handoffs affect ticket or packet truth.
npx claudepluginhub z3z1ma/agent-loom --plugin loomThis skill uses the workspace's default tool permissions.
Git is Loom's implementation isolation and source-history surface.
Enter or repair a Loom workspace before downstream work. Use when repository scope, Loom structure, owner chain, or workspace trust is unclear.
Creates isolated git worktrees for parallel development without disrupting the main workspace. Includes safety verification, .gitignore checks, and directory selection. Use for feature work or PR reviews.
Share bugs, ideas, or general feedback.
Git is Loom's implementation isolation and source-history surface.
Branches, commits, worktrees, remotes, patch stacks, and PRs preserve implementation history and transport work. Use Loom records for the objective, live state, evidence, review, and accepted explanation around that work.
The first Git question is not "what common branch name should I use?" The first Git question is: what integration baseline owns this repository's next change?
That baseline may be a remote-tracking branch, a local branch, a release branch, a fork upstream, a patch-stack parent, a tag, or a specific commit. If Loom cannot identify it from records, repository policy, remote metadata, or operator input, scope fails closed.
loom-shipsource_fingerprint or execution_context needs Git provenancegit status --short, git branch --show-current,
and git remote -v.integration_ref, integration_commit, integration_remote, current
commit, branch, worktree path, push remote, and isolation mode in the Ralph
packet when packetized work is involved.child_write_scope; Git isolation does not
widen Loom write authority.git status --short and git diff before handoff, evidence, commit,
critique, or shipping.Use a separate worktree when two agents or two tickets could otherwise touch the same checkout at the same time.
For parallel Ralph, the normal shape is:
one ticket slice -> one packet -> one branch -> one worktree -> one child
Parallel work is safe only when Loom write scopes and Git worktrees are both independent.
Git can answer:
Git cannot answer by itself:
Read immediately for normal Git-backed Loom work:
references/branch-and-remote-hygiene.md when preparing a branch, checking
freshness, or deciding what integration baseline the work should use.references/worktree-discipline.md when creating, reusing, handing off, or
removing Git worktrees.Then read conditionally:
references/parallel-ralph-with-git.md when multiple Ralph workers, tickets,
repositories, or worktrees may run at once.references/diff-commit-and-merge-hygiene.md when reviewing, staging,
committing, merging, rebasing, or packaging changes.skills/loom-workspace/references/scope-registry.md when repository aliases
or multi-repo scope are unclear.skills/loom-ralph/SKILL.md when Git work is part of a bounded packetized
implementation iteration.