persistent-json-audit-log

A crash-safe audit log uses atomic write operations to prevent partial entries during failures. This Skill generates a persistent JSON log with structured fields like task ID, status, and timestamps to ensure data integrity.

Atomic file writing uses rename operations to guarantee a log file is either fully written or remains unchanged. You need it for structured logging when tracking critical task executions where partial writes could corrupt the audit history.

You can track task dispatches by using mutation functions to log actions, heartbeats, completions, and errors. The log stores structured entries with agent details and output paths, and query functions fetch this history for analysis.

Yes, this audit log operates entirely file-based with no external dependencies. It is suitable for Node.js projects requiring background job monitoring and deployment process tracking without needing a separate database.

The best way to prevent partial writes is employing atomic rename operations during file logging. This approach writes to a temporary file first and renames it, ensuring the operations log remains crash-safe and human-readable.

Operations tracking logs lose data during crashes if they use direct file writes that leave partial entries. Using an audit log with atomic write operations ensures the file is only updated with complete, structured JSON entries.