# Continue Codex Work

Continues interrupted Codex work only after read-codex-history verifies rollout...

- Repository: https://github.com/daymade/claude-code-skills (1509 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add daymade/claude-code-skills --skill continue-codex-work -g -a claude-code -y`
Codex: `npx skills add daymade/claude-code-skills --skill continue-codex-work -g -a codex -y`
Cursor: `npx skills add daymade/claude-code-skills --skill continue-codex-work -g -a cursor -y`
Gemini CLI: `npx skills add daymade/claude-code-skills --skill continue-codex-work -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add daymade/claude-code-skills`

## Description

Continues interrupted Codex work only after read-codex-history verifies rollout identity and fork/compaction lineage, restores the original outcome, unfulfilled requests, and the next action. Use when given a Codex Session ID, asked to pick up a prior Codex run, told Codex was interrupted, fused, compacted or stuck, or asked to take over without `codex resume`. Not for a conversation Codex already natively resumed.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Continue Codex Work

Continue means finish the still-unfulfilled business task. Reading history is a
mandatory evidence phase, not the deliverable.

## Entry gate: external takeover, not native resume

| Current situation | Action |
|---|---|
| Codex itself natively resumed this same conversation, and the restored turns or compaction state are already in the current context | Do not invoke this Skill or `read-codex-history`. Continue directly from the retained context, then verify current workspace and external state before changing anything. |
| A new/different Agent context must take over an earlier Codex rollout, or the user identifies another Session ID whose continuity is not already present here | Use this Skill. Step 1's verified history receipt remains mandatory. |

A restart is not enough to choose the second row. The deciding fact is whether
the current conversation is the host-restored continuation of the same Session,
not whether a Codex process was restarted.

## Step 1: Obtain a verified Codex read receipt

Invoke `daymade-claude-code:read-codex-history` for the exact Session ID and request
the full chronological Session evidence briefing. If the ID is unknown, use that
Skill's inventory or bounded search first.

The receipt must state:

- prompt-ledger, state-index, and rollout sources used;
- selected `session_meta.id` and whether it exactly matches the requested ID;
- root-to-child fork lineage and exact inherited byte boundaries;
- selected and inherited chronological user/assistant turns;
- compacted context, latest plan, end reason, unresolved calls, files, and gaps.

Fail closed on a mismatched rollout, missing child rollout, ambiguous physical copy,
missing parent, broken byte boundary, or continuation cue with no recoverable parent
objective. Never continue from the “closest” file.

## Step 2: Rebuild the continuation contract

The rest: https://github.com/daymade/claude-code-skills/blob/HEAD/daymade-claude-code/continue-codex-work/SKILL.md