원클릭으로
loom-init
Loom root entry for detection, diagnosis, metadata-only adoption, and scenario routing.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Loom root entry for detection, diagnosis, metadata-only adoption, and scenario routing.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Confirm current-head host attestation, hosted delivery gate, required checks, and mergeability.
Confirm current-head host attestation, hosted delivery gate, required checks, and mergeability.
Adopt a repository through Loom metadata and verify the global runtime provider.
Execute a bounded Work Item after host-native admission and before pre-review.
Prepare a session handoff from public derived state without repository mutations.
Bind a real PR, current head, Work Item, branch, and formal worktree before semantic review.
| name | loom-init |
| description | Loom root entry for detection, diagnosis, metadata-only adoption, and scenario routing. |
Use this root scenario to detect the repository state and choose one bounded next scenario. It does not create execution carriers or guess a current item.
loom detect --target <repo> --json.loom doctor --target <repo> --json when installation or provider
readiness is uncertain.loom-adopt.loom status, loom workspace check, or loom route.Repository adoption is metadata-only. Reinforced governance may strengthen host review and validation, but never restores repo work-item, progress, current, review, spec, shadow, or closeout carriers.
Finish when the next scenario, typed subject, formal worktree, and validation boundary are explicit. See ../route-matrix.md.