Continue Codex Work
Continues interrupted Codex work only after read-codex-history verifies rollout...
Install
npx skills add daymade/claude-code-skills --skill continue-codex-work -g -a claude-code -y- Repository
- daymade/claude-code-skills1.5k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 1,602 tokens
- Runs scripts
- No, instructions only
What it does
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.
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.idand 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.
