context-handoff
Save an explicit encrypted development-session handoff for a later Locus chat in the same workspace. Use only when the user invokes $context-handoff or directly asks to capture the current goal, outcome, decisions, changed files, and pending work for another chat.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-23
- Stars
- ★ 22
- Forks
- 1
01 前言 Front Matter
- name
- context-handoff
- description
- Save an explicit encrypted development-session handoff for a later Locus chat in the same workspace. Use only when the user invokes $context-handoff or directly asks to capture the current goal, outcome, decisions, changed files, and pending work for another chat.
- disable-model-invocation
- true
02 资源文件 2
- 参考文档REFERENCES.md425 B
- 参考文档SOURCE.json422 B
03 SKILL.md 正文
Context Handoff
Summarize only the state already established in this session. Do not invent decisions or treat uncertain work as completed.
- Identify the current goal and the concrete outcome so far.
- Capture remaining work or the next checkpoint plainly.
- Call
capture_context_snapshotonce. Locus automatically adds the accepted plan, current todos, and changed-file inventory and encrypts the result in application data. - Confirm what was captured without exposing storage keys or ciphertext.
The snapshot is workspace-isolated and replaces this session's earlier rolling snapshot. Do not create handoff files in the repository.
The native implementation was informed by Context Mode and Claude Mem, but bundles none of their services, hooks, workers, or databases. See REFERENCES.md for attribution.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Prepare a saved implementation plan for a substantial multi-step request.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback