skills.rest
DazedtilDawn
DazedtilDawnCOMMUNITY
Explore all skills by this author →
GitHub

edge-done

Validate coding session saves by cross-checking active_context.yaml and .proof/session_log.jsonl.

Updated Jan 4, 2026
Search Tags:#codex#session#validate#state#proof#end
One-click install
npx skills add https://github.com/DazedtilDawn/operators-edge --skill edge-done
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: edge-done
Source: https://github.com/DazedtilDawn/operators-edge/tree/main/codex/skills/edge-done
Command: npx skills add https://github.com/DazedtilDawn/operators-edge --skill edge-done

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates that a coding session was properly saved by checking the active context state and the existence of proof, ensuring you do not end a session with lost progress.

Core Features & Use Cases

  • Read current state from active_context.yaml and verify required fields exist.
  • Detect any state modifications, such as progressed or completed steps, since session start.
  • Confirm proof of work exists in .proof/session_log.jsonl and summarize entries.
  • Validate plan consistency and detect orphaned or stale pointers to current_step.
  • Generate a concise session summary before ending the session to provide a clear record.

Quick Start

Run edge-done before ending your Codex session to ensure changes are saved and a proof exists.

Frequently Asked Questions about edge-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate that a Codex coding session was properly saved before closing?▼

Validate your saved session by cross-checking active_context.yaml state fields against .proof/session_log.jsonl entries to ensure no unrecorded progress remains before closing the Codex CLI.

What is a session proof and why do I need it when ending a coding task?▼

Session proof is recorded work evidence in .proof/session_log.jsonl. You need it to confirm progressed or completed steps are captured, preventing lost progress when ending coding sessions or switching projects.

How do I check for orphaned pointers to current_step in my active context?▼

Detect orphaned pointers by validating plan consistency in active_context.yaml, which identifies stale references to current_step and ensures the loaded plan matches actual progress state before ending the session.

Can I generate a session summary automatically when finishing a Codex CLI project?▼

Generate a concise session summary to confirm readiness to end the task. This summary provides a clear record by validating active context state and summarizing proof entries before closing the Codex CLI.

What happens if my active_context.yaml state modifications are not recorded in the session log?▼

If active_context.yaml modifications lack matching entries in .proof/session_log.jsonl, validation detects missing proof of work, indicating unrecorded progress and blocking a safe session end until resolved.

Related Skills

Explore More Software Engineering Skills→
DazedtilDawnDazedtilDawn

edge-step

Execute the next step from active_context.yaml and update plan status.

Community
Intermediate
promptrankspromptranks

prk-psv-export

Export validated PSV samples to SQL or JSON for database import.

Official
Intermediate
mutable-state-incmutable-state-inc
72

lean-collab

Orchestrate parallel Lean proof sessions via the lc CLI.

Official
Advanced
visualityplvisualitypl
4

debug

Analyze logs, SQLite database state, and git history to diagnose software issues.

Official
Intermediate