Skip to content
Back to skills

Session Recovery

ASecurity

--- name: session-recovery description: Recover context and continue work after session interruptions or restarts ---

  • 33 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added February 10, 2026
developmentjavascriptgojavabashgit

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add lovedragonball/power-ranger-toolkit --skill session-recovery --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Session Recovery?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Session Recovery
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/lovedragonball-session-recovery/badge)](https://www.skillsdirectory.com/skills/lovedragonball-session-recovery)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# πŸ”„ Session Recovery Skill

---
name: session-recovery
description: Recover context and continue work after session interruptions or restarts
---

## 🎯 Purpose

Seamlessly recover from session interruptions, crashes, or context switches without losing progress.

## πŸ“‹ When to Use

- Starting a new conversation
- After IDE restart
- Switching between projects
- Resuming interrupted work

## 🚨 Recovery Triggers

| Trigger | Action |
|---------|--------|
| New session | Load last context |
| User says "continue" | Resume last task |
| IDE restart | Restore state |
| Crash recovery | Check incomplete tasks |

## πŸ“ Recovery Process

### Step 1: Detect Context
```markdown
Check for:
1. [ ] Active task files (task.md, active.md)
2. [ ] Recent git changes
3. [ ] Unsaved work
4. [ ] Error logs
```

### Step 2: Load Context
```markdown
Read in order:
1. memory/active.md β†’ Current task
2. memory/summary.md β†’ Project context
3. memory/decisions.md β†’ Recent decisions
4. task.md β†’ Pending items
```

### Step 3: Summarize State
```markdown
"Last session you were working on [task].
Progress was [X]% complete.
You were in the middle of [specific action].
Would you like to continue?"
```

### Step 4: Resume or Restart
```markdown
Options:
- Continue from last point
- Start fresh with context
- Switch to different task
```

## πŸ—‚οΈ Context Files

| File | Purpose | Priority |
|------|---------|----------|
| `active.md` | Current task | πŸ”΄ High |
| `task.md` | Task checklist | πŸ”΄ High |
| `summary.md` | Project overview | 🟑 Medium |
| `decisions.md` | Architecture choices | 🟑 Medium |
| `changelog.md` | Recent changes | 🟒 Low |

## πŸ“‹ Recovery Template

```markdown
## πŸ”„ Session Recovery

### Last Session
- **Date**: [date]
- **Duration**: [time]
- **Project**: [name]

### Work in Progress
- Task: [description]
- Progress: [X]%
- Last action: [what was happening]

### Pending Items
- [ ] Item 1
- [ ] Item 2

### Files Modified
- `file1.js` - [changes]
- `file2.css` - [changes]

### Would you like to:
1. Continue from last point
2. Review changes first
3. Start fresh
```

## πŸ”§ Auto-Recovery Features

### 1. State Persistence
```javascript
// Save state before session ends
saveState({
  currentTask: taskName,
  progress: percentage,
  openFiles: fileList,
  recentActions: actionLog
});
```

### 2. Crash Detection
```javascript
// Check for incomplete state
if (activeTask && !taskCompleted) {
  recoveryMode = true;
  loadLastCheckpoint();
}
```

### 3. Git Integration
```bash
# Check uncommitted changes
git status --porcelain

# Get recent commits
git log --oneline -5
```

## πŸ’‘ Best Practices

1. **Save frequently**: Update active.md during work
2. **Checkpoint**: Mark milestones in progress
3. **Commit often**: Small, frequent commits
4. **Document blockers**: Note where you got stuck

## πŸ”— Related Skills

- `memory-system` - Memory management
- `progress-tracking` - Track where you left off
- `git-workflow` - Version control recovery

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…