handoff-in

스타3

포크0

업데이트2026년 6월 29일 00:20

Use when resuming Miller-backed work from a handoff packet or validating a packet before continuing in another harness, model, or session.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

anortham

anortham/miller

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Handoff In

Read a Miller handoff packet, validate it against the current workspace, and produce a compact resume summary. Do not blindly trust stale packet context.

Inputs

If no packet path is supplied, read:

.miller/handoffs/latest.md

Packets should use packet_format: miller-handoff-v1 and live under .miller/handoffs/.

Workflow

Read the packet path and frontmatter. Extract at least:

workspace_root
workspace_id
branch
head
dirty_state
index_built_revision
index_latest_revision

Also extract the packet's changed-file list from the Changed Files section, especially the git status --short and git diff --name-only blocks.

Collect current facts:

workspace(operation="status", format="json")
workspace(operation="health")

git rev-parse --show-toplevel
git branch --show-current
git rev-parse --short HEAD
git status --short
git diff --stat
git diff --name-only

Compare packet facts to current facts:

Workspace root
Branch
HEAD
Dirty state
Exact changed-file list from git status --short
Exact tracked changed-file list from git diff --name-only
Miller index_built_revision / index_latest_revision from index.built_revision and index.latest_revision

Status	Meaning	Action
`safe-to-resume`	Same workspace root, same branch, same HEAD, matching dirty state, matching changed-file list, and Miller health is fresh enough.	Use packet impact/context and continue from `Next Action`.
`drifted-but-resumable`	Same workspace root, but branch, HEAD, dirty state, changed-file list, or Miller index revisions drifted in an explainable way.	Say what drifted, rerun Miller checks, then continue with updated facts.
`blocked`	Packet is missing, root points at a different repo, Miller health is unusable, or drift changes the product intent.	Stop and ask for the smallest needed decision.

When there is a current dirty diff, rerun:

impact(git=true)

When packet context is stale or the next action is vague, rerun:

context(query="<packet goal or next action>", token_budget=<budget>)

Resume Summary

Output a compact summary, not a dump of the whole packet:

## Handoff Intake

status: safe-to-resume | drifted-but-resumable | blocked
packet: <path>
workspace: <current root>
branch/head: <branch> <head>
drift: <none or concrete differences>
miller: <fresh/needs refresh/problem>

## Continue From

<One-paragraph session note summary.>

## Next Action

<The next command, file, test, or Miller call to run.>

Rules

Validate workspace root before using packet instructions.
Treat branch, HEAD, dirty-state, changed-file list, or Miller revision drift as a reason to re-check impact/context, not as proof the packet is useless.
Do not call Goldfish automatically.
Do not include secrets from the packet in the chat transcript.
If the packet points at .miller/handoffs/latest.md but it is missing, report blocked and ask for the packet path.

이 저장소의 다른 Skills

같은 저장소

miller-editing

anortham/miller

Use before changing existing indexed files with Miller edit, especially symbol rewrites, text replacements, renames, or refactors.

2026-07-263

miller-patterns-audit

anortham/miller

Use when an agent needs extractor-recognized code-shape facts such as routes, htmx attributes, Alpine directives, SQL DDL/DML, or data-document structure.

2026-07-243

miller-orientation

anortham/miller

Use when starting a Miller task, choosing a Miller tool, or choosing a Miller search mode.

2026-07-233

miller-bridge-trace

anortham/miller

Use when tracing Miller bridge paths in supported providers: dotnet-web URL literals and fetch/axios client requests to ASP.NET signals, client requests to Next.js route handlers or Nuxt server routes, Next.js/Nuxt route references to file routes, Vue/React references to route definitions, or backend-http client requests to Express/FastAPI/Flask/Django/Spring/Go/gin/echo/Rails/NestJS/Laravel/Phoenix/axum/actix/Symfony/Ktor route facts.

2026-07-183

miller-explore-area

anortham/miller

Use when orienting on an unfamiliar code area with Miller, explaining a module, finding entry points, or gathering context before a change.

2026-07-033

miller-impact-analysis

anortham/miller

Use when assessing blast radius with Miller, choosing tests for a change, answering who uses a symbol, or planning a refactor.

2026-07-033

name	handoff-in
description	Use when resuming Miller-backed work from a handoff packet or validating a packet before continuing in another harness, model, or session.
user-invocable	true
arguments	[packet path]
allowed-tools	mcp__miller__workspace, mcp__miller__impact, mcp__miller__context, mcp__miller__search, mcp__miller__inspect, mcp__miller__trace, Bash

Handoff In

Read a Miller handoff packet, validate it against the current workspace, and produce a compact resume summary. Do not blindly trust stale packet context.

Inputs

If no packet path is supplied, read:

.miller/handoffs/latest.md

Packets should use packet_format: miller-handoff-v1 and live under .miller/handoffs/.

Workflow

Read the packet path and frontmatter. Extract at least:

workspace_root
workspace_id
branch
head
dirty_state
index_built_revision
index_latest_revision

Also extract the packet's changed-file list from the Changed Files section, especially the git status --short and git diff --name-only blocks.

Collect current facts:

workspace(operation="status", format="json")
workspace(operation="health")

git rev-parse --show-toplevel
git branch --show-current
git rev-parse --short HEAD
git status --short
git diff --stat
git diff --name-only

Compare packet facts to current facts:

Workspace root
Branch
HEAD
Dirty state
Exact changed-file list from git status --short
Exact tracked changed-file list from git diff --name-only
Miller index_built_revision / index_latest_revision from index.built_revision and index.latest_revision

Status	Meaning	Action
`safe-to-resume`	Same workspace root, same branch, same HEAD, matching dirty state, matching changed-file list, and Miller health is fresh enough.	Use packet impact/context and continue from `Next Action`.
`drifted-but-resumable`	Same workspace root, but branch, HEAD, dirty state, changed-file list, or Miller index revisions drifted in an explainable way.	Say what drifted, rerun Miller checks, then continue with updated facts.
`blocked`	Packet is missing, root points at a different repo, Miller health is unusable, or drift changes the product intent.	Stop and ask for the smallest needed decision.

When there is a current dirty diff, rerun:

impact(git=true)

When packet context is stale or the next action is vague, rerun:

context(query="<packet goal or next action>", token_budget=<budget>)

Resume Summary

Output a compact summary, not a dump of the whole packet:

## Handoff Intake

status: safe-to-resume | drifted-but-resumable | blocked
packet: <path>
workspace: <current root>
branch/head: <branch> <head>
drift: <none or concrete differences>
miller: <fresh/needs refresh/problem>

## Continue From

<One-paragraph session note summary.>

## Next Action

<The next command, file, test, or Miller call to run.>

Rules

Validate workspace root before using packet instructions.
Treat branch, HEAD, dirty-state, changed-file list, or Miller revision drift as a reason to re-check impact/context, not as proof the packet is useless.
Do not call Goldfish automatically.
Do not include secrets from the packet in the chat transcript.
If the packet points at .miller/handoffs/latest.md but it is missing, report blocked and ask for the packet path.