Skip to content
Back to skills

Session Continue

ASecurity

Continue a workstream from where you left off — faster than /session-start, no focus selection.

  • 13 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsgobashnodegit

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add IlyaGorsky/memory-toolkit --skill session-continue --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Session Continue?

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

Security grade badge for Session Continue
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ilyagorsky-session-continue/badge)](https://www.skillsdirectory.com/skills/ilyagorsky-session-continue)

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
---
name: session-continue
description: Continue a workstream from where you left off — faster than /session-start, no focus selection.
user-invocable: true
argument-hint: "[workstream]"
allowed-tools:
  - Bash(node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" *)
---

# /session-continue — Quick Continue

Pick up a workstream without a full cold start. For cases when you know what you're doing.

---

## Step 1: Find handoff

```bash
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" handoff "$ARGUMENTS"
```

Falls back to global handoff if no per-workstream file exists. Prints `NO_HANDOFF` when neither found.

```bash
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" card "$ARGUMENTS"
```

The workstream's card — what it is, what's open. Read it silently to frame the handoff; `NO_CARD` is fine.

If no handoff exists → suggest `/session-start` instead.

---

## Step 2: Git status (silently)

```bash
git status --short
git log --oneline -3
git branch --show-current
```

If there are uncommitted changes — show in one line.
If the tree is clean — don't mention it.

---

## Step 3: Show summary

Format (10 lines max):

```
## Continuing: {workstream}

**Where we left off:** {from handoff — last action}
**What's next:** {from handoff — next step}
**Branch:** {branch} {uncommitted count if any}

Shall we begin?
```

Don't show task plan, focus candidates, model recommendations — that's for `/session-start`.

---

## Step 4: Load context on demand

**MUST wait for explicit user confirmation ("yes", "go", a number, or similar) before proceeding.** Do NOT auto-continue after showing the summary.

If the user confirmed — load only what's needed for the next step:

- The file that was last edited
- Task plan if available
- Last 3 feedback entries via `node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" search`

Do NOT load the entire memory — only what's relevant.

---

## Step 5: Mark

```bash
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" note "SESSION_CONTINUE branch:$(git branch --show-current) workstream:{name}"
```

---

## Rules

- Maximum speed — 10 lines of output, then get to work
- Don't ask about the model, don't show candidates — the user already knows
- If handoff is older than 7 days — warn: "Handoff from {date}, context may be stale. /session-start for a full overview?"
- If no argument is passed — take the workstream from the latest handoff

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.