Log proof of completed work to the session log. Use after completing significant actions to maintain an audit trail.
Since Codex CLI doesn't have automatic PostToolUse hooks, this skill manually logs proof of completed work.
Call this skill after:
Collect:
Add an entry to .proof/session_log.jsonl:
{
"timestamp": "2025-01-15T14:30:00Z",
"type": "manual_log",
"action": "Completed step 3: Add user authentication",
"files": ["src/auth.py", "tests/test_auth.py"],
"outcome": "success",
"details": "Added JWT-based auth, all tests pass"
}
If .proof/ doesn't exist:
mkdir -p .proof
echo '{"timestamp":"...","type":"manual_log",...}' >> .proof/session_log.jsonl
{
"timestamp": "<ISO 8601 timestamp>",
"type": "manual_log",
"action": "<what was done>",
"files": ["<list>", "<of>", "<files>"],
"outcome": "success | failure | partial",
"details": "<additional context>",
"step": <step number if applicable>
}
For common actions, use these templates:
{
"timestamp": "<now>",
"type": "step_complete",
"step": <N>,
"description": "<step description>",
"proof": "<evidence of completion>"
}
{
"timestamp": "<now>",
"type": "file_change",
"files": ["<path1>", "<path2>"],
"action": "create | edit | delete",
"reason": "<why this change was made>"
}
{
"timestamp": "<now>",
"type": "test_run",
"command": "<test command>",
"result": "pass | fail",
"details": "<N tests, M failures>"
}
The $edge-step skill should call $edge-log after completing each step.
Example workflow:
$edge-step executes the work$edge-log records the proofactive_context.yaml is updated with step completionWithout automatic logging:
Manual logging provides: