with one click
history-log
One-line session history logging format and rules
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
One-line session history logging format and rules
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Standard format for design documents produced by the Architect agent
Standard handoff formats for Task Brief, Checkpoint, Completion, and Verdicts
Merge rules and blocker definition for review coordination
Final-gate artifact audit for AC mapping, necessity, and over-engineering checks.
Analyze OpenCode sessions for user interventions, timeline, and durations
| name | history-log |
| description | One-line session history logging format and rules |
write-history-log to persist the history line.write-history-log is orchestrator-only.write-history-log injects session:<current-session-id> automatically.~/logs/opencode-harness/history/<session-id>.logwrite-history-log creates the history directory if it does not exist.YYYY-MM-DD | project: | session: | task: | files: +/- | agents:<orchestrator=model,...> | tools:<read/edit/bash counts> | total: active: human: | review:<pass/fail> test:<pass/fail> | notes:
agent=model pairs.