audit-logger

Log Create/Update/Delete data changes with before/after snapshots.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/Arnutt-N/hr-ims --skill audit-logger-arnutt-n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-logger
Source: https://github.com/Arnutt-N/hr-ims/tree/main/.claude/skills/audit-logger
Command: npx skills add https://github.com/Arnutt-N/hr-ims --skill audit-logger-arnutt-n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations need immutable, traceable records of data changes to meet security and compliance requirements, but manual logging is error-prone and incomplete.

Core Features & Use Cases

  • Comprehensive audit logging for Create/Update/Delete with before/after snapshots.
  • User attribution, timestamps, and IP/user-agent capture for traceability.
  • Queryable audit history per table, user, or time window for compliance reporting.

Quick Start

Create an audit log entry automatically for any data mutation by integrating the provided Audit helpers and server actions.

Frequently Asked Questions about audit-logger

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

FAQPage Schema
How do I track data changes for compliance audit logs?

Audit logging tracks Create, Update, and Delete operations by capturing before and after snapshots. It automatically records user attribution, timestamps, and IP addresses to build traceable, immutable history for compliance.

What is the best way to implement an audit trail for backend data mutations?

The best way to implement an audit trail is by integrating helper utilities and server actions that automatically log changes with before and after data. This avoids error-prone manual logging and ensures complete records.

Can I query audit history by user or time window for compliance reporting?

Yes, you can query audit history per table, user, or time window for compliance reporting. The system enables queryable history across entities to satisfy security and compliance reporting requirements.

How does user attribution work in audit logging?

User attribution in audit logging works by capturing the user identity, timestamps, and IP or user-agent data during a data mutation. This provides traceability for every record change across the system.

Do I need manual logging to maintain per-record history?

No, you do not need manual logging to maintain per-record history. Automated server actions and audit helpers log changes automatically, preventing the errors and incomplete records common with manual logging.

When do I need immutable audit logs for data changes?

You need immutable audit logs for data changes when your organization must meet strict security and compliance requirements. Immutable, traceable records provide the necessary verification for regulatory reviews.