ai-proj-helper/plugins/reload-session-plugin/skills/SKILL.md

---
name: reload-session
description: Reload a previously saved Claude session to continue the conversation
---

# Reload Session Skill

You are now in session reload mode. Your task is to load a previously saved conversation and help the user continue from where they left off.

## Instructions

1. **Get Session ID**: Extract the session ID from user's request
   - Format: `YYYY-MM-DD_HHmm` (e.g., "2026-01-20_1430")
   - User might provide:
     - Exact ID: "2026-01-20_1430"
     - Partial ID: "0120" or "1430"
     - Title keywords: "the authentication session"
     - Description: "the one about JWT from yesterday"
   - If ambiguous, search `~/.claude/sessions/index.json` and ask for clarification

2. **Find Session File**:
   - First check index.json to find the exact filename
   - Load `~/.claude/sessions/<session-id>_<sanitized-title>.json`
   - If file not found, inform user and offer similar sessions

3. **Load and Parse**: Read the JSON file and extract:
   - Metadata (id, title, date, tags)
   - Summary (context, approach, changes, outcome, next steps)
   - Conversation history (all messages)
   - File modifications

4. **Display Session Context**: Show the user a comprehensive summary:
   ```
   📂 Loaded Session: [Title]

   📅 Original: YYYY-MM-DD HH:mm (X days ago)
   🏷️ Tags: tag1, tag2, tag3
   💬 Messages: X messages
   📝 Modified: file1, file2, file3

   ## Summary

   **Context**: [summary.context]

   **Approach**: [summary.approach]

   **Key Changes**: [summary.keyChanges]

   **Outcome**: [summary.outcome]

   **Next Steps**: [summary.nextSteps]

   ---

   ✅ Session loaded. I have full context of this conversation.
   What would you like to work on?
   ```

5. **Maintain Context**:
   - You now have the full conversation history available
   - Reference specific details from the loaded session when helpful
   - If user asks about the session, you can recall exact details
   - Continue naturally from where the conversation ended
   - Remember all files that were modified
   - Recall all decisions and approaches discussed

6. **Options to Offer**:
   - Continue the last task that was being worked on (from "Next Steps")
   - Review what was accomplished
   - Make changes to previous work
   - Answer questions about the session
   - If work continues, offer to save as a new session or update existing one

## Usage Examples

**By exact ID:**
```
/reload-session 2026-01-20_1430
```

**By partial ID:**
```
reload 0120_1430
reload 1430
```

**By title keyword:**
```
reload the dark mode session
continue the authentication work
```

**By description:**
```
continue the JWT work from yesterday
reload the session about React bugs
```

## Important Notes

- If session file not found, search index.json for similar titles and offer alternatives
- When continuing work, naturally reference the previous conversation context
- If user wants to modify previous work, ask whether to:
  - Save as a new session (recommended to preserve history)
  - Update the existing session (overwrite)
- Show relative dates ("2 days ago", "last week") for better context
- If files were modified in the original session, note if they still exist
- Provide actionable options based on "Next Steps" from the summary

## Example Output

**Successful load:**
```
📂 Loaded Session: Implement User Authentication with JWT

📅 Original: Jan 18, 2026 16:00 (2 days ago)
🏷️ authentication, jwt, security, api
💬 45 messages
📝 Modified: src/auth/jwt.ts, src/middleware/auth.ts, tests/auth.test.ts

## Summary

**Context**: User needed to implement JWT-based authentication for their REST API

**Approach**: Created JWT service with access/refresh tokens, added middleware for route protection

**Key Changes**:
- Implemented JWT token generation and validation
- Added authentication middleware
- Created login/logout endpoints
- Added comprehensive tests

**Outcome**: Authentication system fully implemented and tested with 95% coverage

**Next Steps**: Consider adding password reset functionality and rate limiting

---

✅ Session loaded. I have full context of this conversation.

What would you like to work on?

**Suggested options:**
1. Implement password reset functionality (from Next Steps)
2. Add rate limiting to prevent brute force attacks (from Next Steps)
3. Review or modify the existing authentication code
4. Something else

Let me know and I'll continue from where we left off!
```

**Session not found:**
```
❌ Session "2026-01-99_9999" not found.

Did you mean one of these?

1. [2026-01-20_1430] Implement User Authentication with JWT
   📅 Jan 20, 14:30 | 🏷️ authentication, jwt, security

2. [2026-01-18_1600] Setup OAuth2 Integration
   📅 Jan 18, 16:00 | 🏷️ oauth, authentication, api

To reload: /reload-session <id>
To search: /search-sessions <keywords>
```

**Ambiguous request:**
```
🔍 Found multiple sessions matching "authentication":

1. [2026-01-20_1430] Implement JWT Authentication
2. [2026-01-18_1600] Setup OAuth2 Integration
3. [2026-01-15_1000] Add API Authentication

Which session would you like to reload? (Use the ID)
```