context-resume
恢复之前保存的会话上下文。列出所有待处理的 session,读取选定 session 的任务信息,更新进度,任务全部完成后删除文件。
Best use case
context-resume is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. 恢复之前保存的会话上下文。列出所有待处理的 session,读取选定 session 的任务信息,更新进度,任务全部完成后删除文件。
恢复之前保存的会话上下文。列出所有待处理的 session,读取选定 session 的任务信息,更新进度,任务全部完成后删除文件。
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "context-resume" skill to help with this workflow task. Context: 恢复之前保存的会话上下文。列出所有待处理的 session,读取选定 session 的任务信息,更新进度,任务全部完成后删除文件。
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/context-resume/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How context-resume Compares
| Feature / Agent | context-resume | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
恢复之前保存的会话上下文。列出所有待处理的 session,读取选定 session 的任务信息,更新进度,任务全部完成后删除文件。
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 上下文恢复指南
## 使用场景
在新的 Claude Code 窗口中,需要继续之前未完成的任务时调用此 Skill。
---
## 执行步骤
### Step 1: 列出所有 Session
读取 `docs/context-sessions/` 目录下的所有 `.md` 文件(排除 .gitkeep)。
**输出格式**:
```
📋 待处理的 Session 列表:
1. 20251128-1430-实现用户登录功能.md
未完成任务: 3 项
2. 20251128-1600-修复导出bug.md
未完成任务: 1 项
请告诉我要恢复哪个 session(输入序号或文件名)
```
如果目录为空,输出:
```
📭 当前没有待处理的 session。
所有任务已完成,或尚未使用 context-save 保存过上下文。
```
### Step 2: 读取并展示 Session 内容
用户选择后,读取对应的 session 文件,完整展示内容。
**输出格式**:
```
📂 已加载 Session: {文件名}
---
{session 文件完整内容}
---
🎯 接下来要处理哪个任务?或者需要我继续之前的工作?
```
### Step 3: 开始工作
根据 session 中的信息:
1. 读取关键文件,恢复上下文理解
2. 按优先级处理未完成任务
3. 遵循"下一步行动"的建议
### Step 4: 更新任务进度
每完成一个任务后,**立即更新** session 文件:
1. 将已完成的任务从"未完成"移到"已完成"
2. 更新元信息中的"最后更新"时间
3. 添加新发现的任务(如果有)
**示例更新**:
```markdown
## 已完成任务
- [x] 任务1描述
- [x] 任务2描述
- [x] 🔴 高优先级: 实现 publishArticle 方法 ← 新完成
## 未完成任务
- [ ] 🔴 高优先级: 处理图片上传到微信服务器
- [ ] 🟡 中优先级: 添加发布结果回调
```
### Step 5: 任务完成处理
当所有未完成任务都被完成后:
1. **立即删除** session 文件
2. 输出完成信息
**输出格式**:
```
🎉 Session 所有任务已完成!
已完成任务汇总:
- [x] 任务1
- [x] 任务2
- [x] 任务3
Session 文件已删除: docs/context-sessions/{文件名}
```
---
## 工作流程图
```
┌─────────────────┐
│ 调用 skill │
└────────┬────────┘
│
▼
┌─────────────────┐
│ 列出所有 │
│ session 文件 │
└────────┬────────┘
│
▼
┌─────────────────┐
│ 用户选择 │
│ 要恢复的 │
│ session │
└────────┬────────┘
│
▼
┌─────────────────┐
│ 读取并展示 │
│ session 内容 │
└────────┬────────┘
│
▼
┌─────────────────┐
│ 开始处理任务 │◄──────────┐
└────────┬────────┘ │
│ │
▼ │
┌─────────────────┐ │
│ 完成一个任务 │ │
│ 更新 session │ │
└────────┬────────┘ │
│ │
▼ │
┌────────────┐ │
│ 还有未完成 │───Yes──────┘
│ 任务? │
└─────┬──────┘
│ No
▼
┌─────────────────┐
│ 删除 session │
│ 文件 │
└─────────────────┘
```
---
## 命令快捷方式
在恢复 session 后,可以使用以下指令:
| 指令 | 作用 |
|------|------|
| `继续` | 按优先级继续处理下一个任务 |
| `更新进度` | 手动触发 session 文件更新 |
| `查看剩余` | 显示剩余未完成任务 |
| `换窗口处理-` | 再次保存并切换窗口 |
---
## 注意事项
1. **及时更新** - 每完成一个任务立即更新 session 文件
2. **保持文件同步** - 如果发现新任务,添加到未完成列表
3. **删除确认** - 只有当所有任务完成才删除文件
4. **关键文件** - 恢复时优先读取 session 中列出的关键文件Related Skills
json-to-llm-context
Turn JSON or PostgreSQL jsonb payloads into compact readable context for LLMs. Use when a user wants to compress JSON, reduce token usage, summarize API responses, or convert structured data into model-friendly text without dumping raw paths.
opencontext
Persistent memory and context management for AI agents using OpenContext. Keep context across sessions/repos/dates, store conclusions, and provide document search workflows.
hig-project-context
Create or update a shared Apple design context document that other HIG skills use to tailor guidance. Use when the user says 'set up my project context,' 'what platforms am I targeting,' 'configure HIG settings,' or when starting a new Apple platform project.
ddd-context-mapping
Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.
context7-auto-research
Automatically fetch latest library/framework documentation for Claude Code via Context7 API
context-window-management
Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long context.
context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI orchestration.
context-management-context-save
Use when working with context management context save
context-management-context-restore
Use when working with context management context restore
context-driven-development
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.
code-refactoring-context-restore
Use when working with code refactoring context restore
c4-context
Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies. Synthesizes container and component documentation with system documentation to create comprehensive context-level architecture. Use when creating the highest-level C4 system context documentation.