checkpoint-read
Skill4 starsChanged 23 days agoMITView on GitHub
Read a saved session checkpoint to understand prior work for continuation, review, or questions without modifying files.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- SnowyLake/snowy-agent-skillsword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- SnowyLake/snowy-agent-skills★ 4100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- checkpoint-saveSkill
- cursor-cliSkill
- grok-cliSkill
- hybrid-workSkill
- snapdragon-profiler-statisticsSkill
- unity-shader-analysisSkill
The file
Files
checkpoint-read
目录
- 目标与边界
- 会话文件夹解析
- 读取
- 完成与后续工作
目标与边界
读取指定会话的 checkpoint, 理解其目标, 状态, 决策, 约束和工作产物, 为续接, 审查或回答问题提供背景. 读取阶段只读, 不复制 checkpoint, 创建会话文件夹或修改任何文件. 当前任务以用户本次要求为准, 不自动接管来源会话的目标和 TODO.
本 skill 依赖 checkpoint-save 的 checkpoint-contract.md. 读取其中的共享规则, 按需查看文件与章节含义; 不必为只读读取加载全部写入格式. 若文件不可用, 停止并提示先安装 checkpoint-save, 不凭记忆重建契约.
会话文件夹解析
解析本次读取的来源会话文件夹:
- 如果用户没有指定会话文件夹, 解析当前会话文件夹.
- 如果用户指定了会话文件夹, 将其作为读取来源, 无论当前会话是否已有 checkpoint, 都允许读取.
- 如果当前文件夹不明确且用户未指定路径, 要求用户指定一个已有会话文件夹.
读取来源与当前会话自己的文件夹分别识别. 读取其他会话不会切换当前会话文件夹, 也不会改变后续 checkpoint-save 的保存位置. 用户明确指定共享文件夹作为当前会话文件夹时, 才按该指定保存.
读取
- 优先读取
CONTEXT.md, 用Work Artifacts定位此前工作范围. 需要理解决策背景, 排障依据, 已拒绝方案或历史不确定性时, 再读取相关HISTORY.md条目. - 只核对影响当前请求的关键项目事实, 不为读取而重新调查整个工程. 区分 checkpoint 记录, 已核对的现状和推断, 不把未验证假设当作事实.
- 只有
CONTEXT.md时读取该快照. 只有HISTORY.md时尽可能重建背景, 说明缺少当前快照, 不把旧历史直接当作当前状态. 两个文件都不存在时报告没有可用 checkpoint, 不宣称读取成功. - 若文件不完整或存在冲突, 按共享规则判断信息来源, 指出影响当前请求的缺失, 过时记录或不确定性, 不改写源文件.
完成与后续工作
根据当前请求简要说明读取来源, 来源会话的目标与进度, 以及相关的关键约束或阻塞. 仅在存在重要缺失, 冲突或推断时说明依据和不确定性; 不固定输出置信度模板, 不默认逐段复述快照. 用户要求完整状态时再展开.
- 单独请求读取时, 读取完成后结束.
- 用户同时要求读取并审查时, 继续核对实际文件, 改动和必要验证.
Work Artifacts只用于定位范围, checkpoint 中的完成说明和验证结论不能代替独立审查. - 用户同时要求读取并续接或回答问题时, 完成读取后执行已授权的后续任务, 不再次请求同一授权.
- 仅从 checkpoint 读到 TODO 不构成执行授权; 读取未完成或关键信息不足时, 不据此开始依赖这些信息的工作.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

