continue claude work

Other Community

Skill notes

Overview

Recover actionable context from a prior Claude Code session and continue execution in the current conversation. Use local session files as the source of truth, then continue with concrete edits and checks — not just summarizing. Why this exists instead of claude --resume: claude --resume replays the full session transcript into the context window. For long sessions this wastes tokens on resolved issues and stale state. This skill selectively reconstructs only actionable context — the latest compact summary, pending work, known errors, and current workspace state — giving a fresh start with prior knowledge.

File Structure Reference

For directory layout, JSONL schemas, and compaction block format, see references/file_structure.md.

Step 1: Extract Context (single script call)

Run the bundled extraction script. It handles session discovery, compact-boundary parsing, noise filtering, and workspace state in one call: The script outputs a structured Markdown briefing containing: Session metadata from sessions-index.json Compact summary — Claude's own distilled summary from the last compaction boundary (highest-signal context) Last user requests — the most recent explicit asks

Step 2: Branch by Session End Reason

The briefing includes a Session end reason. Use it to choose the right continuation strategy: End Reason · Strategy Clean exit · Session completed normally. Read the last user request that was addressed. Continue from pending work if any. Interrupted · Tool calls were dispatched but never got results (likely ctrl-c or timeout). Retry the interrupted tool calls or assess whether they are still needed.

Step 3: Reconcile and Continue

Before making changes: Confirm the current directory matches the session's project. If the git branch has changed from the session's branch, note this and decide whether to switch. Inspect files related to pending work — verify old claims still hold. Do not assume old claims are valid without checking.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daymade · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Extract Context (single script call)

Run the bundled extraction script. It handles session discovery, compact-boundary parsing, noise filtering, and workspace state in one call: The script outputs a structured Markdown briefing containing: Session metadata from `sessions-index.json` Compact summary — Claude's own distilled summary from the last compaction boundary (highest-signal context) Last user requests — the most recent explicit asks

02
Step 2: Branch by Session End Reason

The briefing includes a Session end reason. Use it to choose the right continuation strategy: End Reason · Strategy Clean exit · Session completed normally. Read the last user request that was addressed. Continue from pending work if any. Interrupted · Tool calls were dispatched but never got results (likely ctrl-c or timeout). Retry the interrupted tool calls or assess whether they are still needed.

03
Step 3: Reconcile and Continue

Before making changes: Confirm the current directory matches the session's project. If the git branch has changed from the session's branch, note this and decide whether to switch. Inspect files related to pending work — verify old claims still hold. Do not assume old claims are valid without checking.

04
Step 4: Report

Respond concisely: Context recovered: which session, key findings from the briefing Work executed: files changed, commands run, test results Remaining: pending tasks, if any

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.