belt
Handoff carrier that moves durable context between agents or threads with concise state, proof, risks, and next actions, covering handoff, thread-control, and resume flows through lenses. Use when writing a handoff, deciding whether to continue or start a new thread, or resuming a repo task from durable state.
- License 许可
- MIT
- 最近更新
- 2026-07-23
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- belt
- metadata
- { "version": "0.2.1", "changelog": "0.2.1 - add trigger eval corpus for handoff, thread-control, and resume activation" }
- description
- Handoff carrier that moves durable context between agents or threads with concise state, proof, risks, and next actions, covering handoff, thread-control, and resume flows through lenses. Use when writing a handoff, deciding whether to continue or start a new thread, or resuming a repo task from durable state.
02 资源文件 11
- 参考文档AGENTS.md1.6 KB
- 参考文档evals/evals.json2.8 KB
- 参考文档exemplars/pr-belt.md242 B
- 参考文档references/agent-judgment.md774 B
- 参考文档references/coverage-gaps.md242 B
- 参考文档references/glossary.md525 B
- 参考文档references/lens-handoff.md2.1 KB
- 参考文档references/lens-resume.md1.7 KB
- 参考文档references/lens-thread-control.md2.2 KB
- 参考文档references/patterns.md765 B
- 参考文档references/rules.md2.6 KB
03 SKILL.md 正文
Belt
Use when moving durable context between agents/threads with concise state, proof, risks, and next actions, covering handoff, thread-control, and resume flows through lenses, within the active issue, PR, or workflow packet.
Operating Contract
- Role: Handoff carrier.
- Canonical name:
belt; never render this package withomp-,codex-, orclaude-prefixes. - Primary modes:
shape,review. - After this entrypoint, load
AGENTS.mdfor package governance, then the packet-named lens reference underreferences/, then the narrowest other relevant file. - Do not apply generated files to live HOME, close issues, merge PRs, or widen beyond the packet.
Request Modes
shape: follow the shape boundary in the shared nucleus contract.review: follow the review boundary in the shared nucleus contract.
Lenses
The input packet may carry a lens field. A named lens loads references/lens-<name>.md; when lens is absent, load the mode default. Lenses select guidance only; they never widen packet scope or change the mode boundary.
handoff(default): compact the current work into a durable handoff document for a fresh agent. Loadsreferences/lens-handoff.md.thread-control: decide whether to continue in the current thread or start a new one (absorbed from the retiredthread-controlskill). Loadsreferences/lens-thread-control.md.resume: re-orient in an existing repo task from durable state before any edits (absorbed from the retiredresume-threadskill). Loadsreferences/lens-resume.md.
Decision Authority
- User goal and explicit constraints.
- Active issue or PR acceptance criteria.
- Verified repository code, tests, and live PR state.
- Routed references in this package.
- Accepted exemplars.
- General heuristics.
Workflow
- Resolve mode, packet scope, and lens before acting.
- Load the named lens reference (or the default
lens-handoff.md), plus only the other references needed for the target surface. - Execute the smallest coherent step allowed by the packet and lens.
- Return the required output packet and any coverage gaps.
Standards or Rules
- Required input packet fields:
current state,lens,changed files,proof,risks,next action. - Required output packet fields:
handoff,proof summary,blockers,resume command/context. - Do not include transcripts by default; do not omit blockers.
Review Output
Report mode, lens, target surface, loaded references, rule IDs, proof run, and unresolved coverage gaps.
04 同仓库更多 Skills
good-skill
Use when validating a known-good version-controlled skill fixture.
zero-prerelease
Valid zero prerelease fixture. Use when validator tests accept zero numeric prerelease identifiers.
zero-alpha-prerelease
Valid alphanumeric prerelease fixture. Use when validator tests accept leading digits in alphanumeric prerelease identifiers.
alpha-one-prerelease
Valid prerelease fixture. Use when validator tests accept dotted alphanumeric prerelease identifiers.
handoff
Use when testing collision with an existing global handoff skill.
missing-version
Missing version fixture. Use when validator tests reject absent metadata versions.