# Save Session Context for Handoffs

Long AI coding sessions can lose important decisions when work moves to a new window. This skill creates a structured handoff note with completed work, pending tasks, key files, and next steps.

## Install

```bash
npx skillstore add claudate/context-save
```

## Metadata

- - Slug: claudate-context-save
- - Version: 1.0.0
- - Author: Claudate
- - GitHub username: Claudate
- - License: MIT
- - Repository: https://github.com/Claudate/claude-code-context-sync/tree/main/skills/context-save
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: filesystem
- - Quality score: 72
- - Public page: https://skillstore.pages.dev/skills/claudate-context-save
- - Manifest: https://skillstore.pages.dev/api/skills/claudate-context-save/manifest

## Capabilities

- Detects a specific user request to save context before switching windows.
- Summarizes the current task, completed work, pending work, and next actions.
- Formats the handoff as a Markdown session document.
- Stores the handoff under docs/context-sessions/ using a timestamped filename.
- Reports the saved path and the number of unfinished tasks.

## Use Cases

- Developer Window Handoff: Save implementation progress before moving a long coding task to a fresh AI window.
- Team Continuity Notes: Create a clear task summary that another teammate can review before continuing work.
- Project Session Archive: Keep lightweight records of active project decisions, open tasks, and important files.

## Prompt Templates

### Save Basic Context

```
换窗口处理- Please save the current session context with completed tasks, pending tasks, key files, and next steps.
```

### Save With Priority Review

```
换窗口处理- Save the current context and group unfinished tasks by high, medium, and low priority.
```

### Save Technical Decisions

```
换窗口处理- Save the current context, including important technical decisions, known problems, and files the next window should inspect first.
```

### Save Redacted Handoff

```
换窗口处理- Save a context handoff, but redact secrets, tokens, private customer data, and credentials before writing the session file.
```

## Limitations

- It depends on the agent accurately summarizing the active conversation.
- It does not automatically redact secrets or private business context.
- It does not restore context by itself; a separate resume workflow is expected.
- It can create repository files that may be committed unless reviewed.

## Best Practices

- Review the generated note before committing it to a shared repository.
- Ask for redaction when the conversation includes credentials or private data.
- Use specific task names so session files are easy to find later.

## Anti Patterns

- Do not save raw secrets, tokens, credentials, or customer data.
- Do not treat the saved handoff as a verified project specification.
- Do not rely on this skill as the only record for critical decisions.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T22:02:07.419\+00:00
- - Summary: Static command-execution, weak-crypto, reconnaissance, and entropy findings are false positives caused by Markdown backticks, readable Chinese prose, and example text. The confirmed risk is that the skill directs agents to persist session summaries into repository files, which can accidentally retain secrets or proprietary context.

## Stats

- - Views: 193
- - Downloads: 13
- - Favorites: 0
- - Popularity score: 0