edge-log

Name: edge-log
Availability: InStock
Author: dazedtildawn

Log structured proof entries to .proof/session_log.jsonl for audit trails.

Updated Jan 4, 2026

Search Tags:#workflow #development #verification #log #session-log #audit-trail #proof

Ready to run

npx skills add https://github.com/DazedtilDawn/operators-edge --skill edge-log

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: edge-log
Source: https://github.com/DazedtilDawn/operators-edge/tree/main/codex/skills/edge-log
Command: npx skills add https://github.com/DazedtilDawn/operators-edge --skill edge-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides an auditable trail by logging proof of significant actions to the session log, ensuring accountability and traceability for every step.

Core Features & Use Cases

Manual logging for completed work when automatic hooks are unavailable.
Appends entries to .proof/session_log.jsonl with structured JSON.
Creates .proof directory if needed and preserves an immutable audit trail for audits and debugging.

Quick Start

After completing a significant action, call edge-log to record a new proof entry in the session log.

Frequently Asked Questions about edge-log

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

FAQPage Schema

How do I create an audit trail for development workflow steps?▼

An audit trail logs proof of completed work to a session log, ensuring accountability. You append structured JSON entries with timestamps, actions, and outcomes to a session_log.jsonl file to maintain a traceable development history.

What is the best way to log proof of file changes and tests for later verification?▼

Logging proof of file changes and tests requires appending structured entries to a JSONL file. You record the timestamp, action type, modified files, and test outcomes after significant workflow steps to create an immutable history for verification.

How do I manually write structured session logs when automatic hooks are unavailable?▼

Manually write structured session logs by calling a logging utility after completing significant actions. This appends JSON entries with timestamp, type, action, files, outcome, and details to a .proof/session_log.jsonl file, creating a directory if needed.

Does the session log use a standard schema for downstream tooling ingestion?▼

The session log uses a defined JSON schema for timestamp, type, action, files, outcome, and details. Writing entries to JSONL format enables easy ingestion by downstream tooling for auditing and debugging purposes.

When do I need to record entries in a session log during a development workflow?▼

Record entries in a session log after completing significant actions across workflow steps, file changes, and tests. Apply logging at these checkpoints to maintain a traceable history and ensure accountability for every development action.

Why use JSONL format for an audit trail instead of a standard log file?▼

Using JSONL format for an audit trail appends structured JSON objects line by line, preserving an immutable history. This format enables easy ingestion by downstream tooling compared to unstructured standard log files.