Save session context

VerifiedSafe

Updates task tracking (tk) and AI documentation files (ai/) to persist session state. Logs findings, marks tasks complete, creates new tasks, then updates status, design, decisions, and sprint files. Helps capture progress before context switches or session end.

Sby Skills Guide Bot
ProductivityIntermediate
506/2/2026
Claude Code
#session-management#context-save#task-tracking#ai-files

Recommended for

Our review

Persists session state by updating ai/ files and tk tasks, then committing changes.

Strengths

  • Automates context persistence between sessions
  • Manages tasks with tk (add, complete, log)
  • Keeps documentation files (STATUS, DESIGN, etc.) tidy
  • Includes a structured git commit

Limitations

  • Depends on the tk tool for task management
  • Assumes an existing git repository
  • Can be overkill if little has changed in the session
When to use it

At the end of a session, before switching context, or explicitly to snapshot current state.

When not to use it

When the project does not use tk or have a git repo, or you do not want to record state.

Security analysis

Safe
Quality score88/100

The skill uses bash and git commands for legitimate context-saving purposes, with no destructive or exfiltrating actions.

No concerns found

Examples

Save session state
Save the current context to ai/ files and update tk tasks, then commit.
Save before compacting
Before compacting the conversation, run the save skill to persist what we've done.

name: save description: Update ai/ files and tk tasks. allowed-tools: Read, Write, Edit, Glob, Grep, Bash

Context Save

Persist session state to ai/ and tk. Priority: tk and ai/ first (from context), git last.

Trigger: Before /compact, session end, context switch, or explicitly.

1. Update tk Tasks

tk ls

For each task:

  • Log findings first: tk log <id> "what was learned" — errors, root cause, file paths
  • Mark complete: tk done <id>
  • Add new: tk add "title" -d "context"

Don't leave stale tasks.

2. Update ai/

STATUS.md (always): Current focus, blockers, what worked. Prune stale content.

DESIGN.md (if architecture changed): Components, patterns, interfaces.

DECISIONS.md (if decisions made): Context → Decision → Rationale.

SPRINTS.md (if sprint progress): Mark completed, update status.

Keep files <500 lines. Move details to subdirs if needed.

3. Commit

git add ai/ .tasks/
git commit -m "Update session context"

4. Report

## Saved

Tasks: [N done, N added, N pending]
ai/: [what changed]

## Next Session

[2-4 bullets: what to do next based on pending tasks, blockers, incomplete work]
Related skills