360 Secure SkillHub
360 安全技能中心

pre-compact

在上下文压缩或清空前,把后续会话所需信息写入 .agents/compact-handoff/ 下的交接文件,含位置、下一步、决策、发现、开放问题、未完成指令等;随后检查项目文档与全局 agent 指令文件,列出缺失或过期项并给出修改建议,等待确认或按 auto 模式直接应用,最后输出 READY 行。

tenequm
tenequm
热度 44.48
最近更新 2026-08-21 20:12:04
分类:知识依赖:读写文件 / 内部调用大模型应用场景:笔记整理 / 工作流 / 任务管理 / 摘要总结

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add tenequm/pre-compact
Metadata
name
pre-compact
description
Prepare the session for context compaction - write a handoff file a fresh session can continue from, propose updates to the project's durable docs, apply them on approval or with `auto`. Use before compacting or clearing context, or on "pre-compact".
metadata
{"version":"0.1.3","categories":"agents, productivity","topics":"context, handoff, compaction, session-state, documentation","openclaw":{"homepage":"https://github.com/tenequm/skills/tree/main/skills/pre-compact","emoji":"🧳"}}
disable-model-invocation
true
argument-hint
[auto|a]

I will compact this context soon. The summary can be wrong. Files are the source of truth. Move everything a fresh session needs from this conversation into files. Mode: $ARGUMENTS. auto or a means: apply all proposed updates without asking.

Write .agents/compact-handoff/YYMM-DD-HHMM-<short-slug>.md. Start with the line # Handoff <date> <time> <repo>@<branch>. Then write these sections:

  • Position: what we are doing, why, and where we stopped.
  • Next steps: in order, with the paths, commands and identifiers needed to run them.
  • Decisions: each decision made here, with its reason.
  • Findings: what we learned works or fails, verbatim.
  • Open questions: numbered, each with your recommended answer.
  • Undone instructions: what I asked for that is not done.
  • References: files, links, related docs.

Copy numbers, commands and paths exactly. Do not paraphrase them. Never write secrets, tokens, passwords or API keys into the handoff. Write where they live instead, for example the env var name or the vault item. Record only decisions that were made. Keep open questions open.

Then check the docs this project uses to track work: plans, journals, status sections, task lists. For each item in the handoff, ask: is it recorded there, and is it current? Do not ask me what the repo can answer.

Also check my global agent instructions (~/.claude/CLAUDE.md, AGENTS.md, or the equivalent for this harness) for the marker <!-- pre-compact -->. If the marker is absent, add this item: insert the line below verbatim.

  • After compaction, read the handoff file named in the summary (.agents/compact-handoff/) before you trust the summary. The summary can be wrong. The handoff file is the source of truth.

List what is missing or stale as numbered items. Give the file and the change, one line each. Then ask: y = apply all, n = apply none, numbers = apply those, or tell me what to change. Wait for my answer, unless in auto mode. Never commit. Never push.

Finish with one line: READY, the handoff path, and the files you changed.