Individual skill

continue-claude-code-work

Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action. Use when given a Claude Code Session ID, asked to pick up prior Claude work, told a run was interrupted or compacted, or asked to take over without `claude --resume`. Not for Codex sessions (use continue-codex-work).

daymade-claude-code/continue-claude-code-work/SKILL.md

Read pinned source

Source commit 7c4d326ddd94d504e00e241ba49498e95160afbe

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,522
Repository last updated: Nov 6, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 4,238 bytes

Read excerpt


# Continue Claude Code Work

Continue means execute the still-unfinished business task. It does not mean
summarize the transcript, perfect the history tool, or start a new experiment.

## Step 1: Obtain a verified read receipt

Invoke `daymade-claude-code:read-claude-code-history` for the exact Session. Ask
that Skill for a chronological evidence briefing, not separate “last user” and
“last assistant” buckets. If the Session ID is unknown, use its search/inventory
route first.

Do not act until the receipt states: