Generates database audit logging implementation for compliance tracking, supporting trigger-based, application-level, CDC, and database log strategies.
How this command is triggered — by the user, by Claude, or both
Slash command
/database-audit-logger:audit-logThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Database Audit Logger Track database changes for compliance and debugging. ## Audit Strategies 1. **Trigger-Based**: Database triggers on INSERT/UPDATE/DELETE 2. **Application-Level**: Log in application code 3. **CDC (Change Data Capture)**: Stream changes 4. **Database Logs**: Parse database transaction logs ## Audit Table Template ## When Invoked Generate audit logging implementation for compliance tracking.
Track database changes for compliance and debugging.
CREATE TABLE audit_log (
id SERIAL PRIMARY KEY,
table_name VARCHAR(100) NOT NULL,
operation VARCHAR(10) NOT NULL,
old_data JSONB,
new_data JSONB,
user_id INTEGER,
timestamp TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);
-- Trigger example
CREATE OR REPLACE FUNCTION audit_trigger()
RETURNS TRIGGER AS $$
BEGIN
INSERT INTO audit_log (table_name, operation, old_data, new_data)
VALUES (TG_TABLE_NAME, TG_OP, row_to_json(OLD), row_to_json(NEW));
RETURN NEW;
END;
$$ LANGUAGE plpgsql;
Generate audit logging implementation for compliance tracking.
npx claudepluginhub earth-treasure-inc/claude-code-plugins-plus-skills-1d8dce0c --plugin database-audit-logger35plugins reuse this command
First indexed Dec 31, 2025
Showing the 6 earliest of 35 plugins
/audit-logGenerates database audit logging implementation for compliance tracking, supporting trigger-based, application-level, CDC, and database log strategies.
/stored-procGenerates production-ready stored procedures, functions, and triggers for PostgreSQL, MySQL, and SQL Server, with input validation, error handling, and transaction safety.
/auditAudits specified target (e.g., user access logs) for compliance with optional framework (e.g., SOC2, GDPR), producing logging and tracking reports for enterprise requirements.
/plan-migrationPlan safe schema migration with backward compatibility and rollback strategy.
/fire-migrate-databaseGuides migration between PostgreSQL, MySQL, SQLite, and SQL Server through a 6-step pipeline: assess, plan, execute, and verify. Accepts optional direction, source, and target arguments.
/db-diffCompares PostgreSQL and MySQL database schemas, detects all differences (tables, columns, indexes, constraints, triggers), and generates safe migration scripts with rollback.