메뉴
How to expose a long-running local dev/test server from a Shepherd worktree so the operator's live preview finds it, by writing the port to a `.shepherd-preview` file. Load when starting a dev server, test server, or any other long-running local preview in this session.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
How a Shepherd session opens a pull request - exactly one PR per session, what to do when the work is too large for one (promote to an epic, or ship a slice plus a follow-up issue), and how to declare manual operator steps so they survive merge. Load before running `gh pr create`, or as soon as a task looks like it needs more than one PR.
Onboard a repo into Shepherd's work-execution model — turn a PRD or stated goals into a drainable backlog of issues/epics (tracer-bullet vertical slices, epic-dag dependencies) and seed repo-specific agent instructions, then point at the first task to drain. Use when onboarding an existing codebase to Shepherd, bootstrapping a greenfield project from a PRD, or asked to turn intent into Shepherd-shaped issues/epics.
Review all open PRs for plausibility, validity and product-fit, propose a merge order, then merge on approval. Use when asked to "work through the open PRs", "review and merge the PR queue", "run the merge train", or triage what should land next.
SOC 직업 분류 기준
| name | shepherd-preview |
| description | How to expose a long-running local dev/test server from a Shepherd worktree so the operator's live preview finds it, by writing the port to a `.shepherd-preview` file. Load when starting a dev server, test server, or any other long-running local preview in this session. |
Shepherd can proxy a dev server running in this worktree to the operator's browser (and, when enabled, onto the tailnet). It finds the server by port.
If you start a long-running dev server in this worktree and want Shepherd's live preview to target
a specific port, write that port — a bare number, nothing else — to a file named
.shepherd-preview in the repository root.
Shepherd uses that value only when the port is actually listening; otherwise it auto-detects the port. So this is optional: skip it if you have no dev server, or if the default detection already targets the right port.
tailscale serve yourself.Verify, in this order:
.shepherd-preview contains the actual listening port (a bare number);ss -ltnp | grep <port>).Remember that a backgrounded server outlives the step that needed it: kill what you spawn in the same shell once you are done with it.