agent-context-transfer
Transfer implementation context to a fresh agent for seamless handoff
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 2
01 前言 Front Matter
- name
- agent-context-transfer
- category
- productivity
- metadata
- { "hermes": { "requires_tools": [ "read_file", "write_file", "terminal", "skill_view", "search_files" ], "requires_plugins": [], "requires_toolsets": [] } }
- description
- Transfer implementation context to a fresh agent for seamless handoff
02 资源文件 3
- 参考文档references/context-checklist.md3.6 KB
- 脚本scripts/verify-handoff.sh2.6 KB
- 参考文档templates/briefing-template.md5.9 KB
03 SKILL.md 正文
Agent Context Transfer Skill
Use when a fresh agent needs to continue work on a multi-session implementation. Provides a standardized briefing template, verification checklist, and handoff protocol.
Purpose
Eliminate context loss when switching agents or sessions. Captures:
- Current implementation state (what's done/verified/broken)
- Required skills and loading order
- Verification contract (tests that must stay green)
- Remaining work with dependencies
- Critical gotchas and pitfalls
- Ready-to-use prompt template for the fresh agent
Files
templates/briefing-template.md— Reusable briefing templatescripts/verify-handoff.sh— Auto-verifies handoff completenessreferences/context-checklist.md— What must be included in any handoff
Usage
# As the OUTGOING agent: create briefing from template
bash ~/.hermes/skills/agent-context-transfer/scripts/verify-handoff.sh create
# As the INCOMING agent: load this skill + read the briefing
skill_view(name='agent-context-transfer')
read_file("~/.hermes/skills/agent-context-transfer/templates/briefing-template.md")
Handoff Protocol
- Outgoing agent fills template with current state
- Outgoing agent runs
verify-handoff.sh validate— checks all required sections present - Outgoing agent commits briefing to repo (or shares via mnemon/memory)
- Incoming agent loads this skill, reads briefing, loads listed skills, begins verification
04 同仓库更多 Skills
version-single-source
Use when adding a new component dependency or versioning a binary in install/boot scripts.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
shell-path-login
Use when a binary or script works in one shell context but not another (interactive vs non-interactive login vs non-login shell).
self-update-fix
Fix a failing dependency update PR. Use when a self-update PR's CI fails, or when invoked by scripts/self-update-fix.sh.
pr-change-log
Use when a multi-commit PR needs its description written/updated, or when closing out a long branch with many fix commits.
persistent-knowledge
Persistent skills/knowledge in Codespace via symlinks.