用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/majiayu000/claude-skill-registry --skill recover命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | recover |
| version | 1.0.0 |
| description | [Utilities] Restore workflow context from checkpoint after session loss |
| activation | user-invoked |
[IMPORTANT] Use
TaskCreateto break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI may ask user whether to skip.
Goal: Restore workflow state and todo items from checkpoint files after context loss or session interruption.
Workflow:
memory-checkpoint-*.md in reports directoryKey Rules:
plans/reports/ and plan-specific report directoriesRestore workflow state and todo items from checkpoint files after context compaction or session loss.
Use this command when:
Look for checkpoint files in the reports directory:
ls -la plans/reports/memory-checkpoint-*.md | tail -5
Or search for all recent checkpoints:
find plans -name "memory-checkpoint-*.md" -mmin -60 | head -5
Read the most recent checkpoint to understand the saved state:
Read the checkpoint file at: plans/reports/memory-checkpoint-YYMMDD-HHMMSS.md
The checkpoint file contains a JSON metadata block at the end:
{
"sessionId": "...",
"activePlan": "plans/YYMMDD-slug/",
"workflowType": "feature",
"currentStep": "cook",
"remainingSteps": ["test", "code-review"],
"pendingTodos": [...]
}
IMMEDIATELY call TaskCreate with the pending todos from the checkpoint:
[
{ "content": "[Workflow] /cook - Implement", "status": "in_progress", "activeForm": "Executing /cook" },
{ "content": "[Workflow] /test - Run tests", "status": "pending", "activeForm": "Executing /test" },
{ "content": "[Workflow] /code-review - Review code", "status": "pending", "activeForm": "Executing /code-review" }
]
If activePlan is set in the metadata, read the plan file:
Read: {activePlan}/plan.md
Resume from the currentStep identified in the metadata. Execute the remaining workflow steps in order.
| Scenario | Recovery Type | Trigger |
|---|---|---|
| Session resume after compact | Automatic | post-compact-recovery.cjs hook |
| New session in same directory | Manual | This /recover command |
| Explicit user request | Manual | This /recover command |
| No workflow state found | Manual | This /recover command |
Checkpoints are saved to different locations based on context:
{plan-path}/reports/memory-checkpoint-*.mdplans/reports/memory-checkpoint-*.md/checkpoint - Create a manual checkpoint (before expected loss)/compact - Manually trigger context compaction/context - Load project context/watzup - Generate progress summaryUser: /recover
Claude: Let me find and restore your workflow context.
1. Finding latest checkpoint...
Found: plans/reports/memory-checkpoint-260110-143025.md
2. Reading checkpoint metadata...
- Workflow: feature
- Current step: /cook
- Remaining: /test, /code-review
- Active plan: plans/260110-1430-new-feature/
3. Restoring TaskCreate items...
[Calling TaskCreate with 3 pending items]
4. Reading active plan...
[Reading plans/260110-1430-new-feature/plan.md]
5. Ready to continue from /cook step.
Shall I proceed with the implementation?
IMPORTANT Task Planning Notes (MUST FOLLOW)