Database Audit Logger Skill for Transactional PostgreSQL History
Record selected before-and-after fields from an owned test database and verify how audit history behaves on rollback.
中文Install in Claude Code
Use a disposable PostgreSQL instance, psql, synthetic inventory, and documented audit fields.
- Get the complete `plugins/database/database-audit-logger/skills/implementing-database-audit-logging` directory from the pinned GitHub commit.
- Copy it into the target project's `.claude/skills/`. Check `.claude/skills/implementing-database-audit-logging/SKILL.md`, start Claude Code at the project root, and call `/implementing-database-audit-logging`.
Example task
Commit mug-01 quantity 5 to 8, then change 8 to 9 in a separate transaction and roll it back. Inspect inventory and audit rows.What to check
Quantity stays at 8. The audit shows only the committed change from 5 to 8.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should a trigger record every field from the entire row?
Choose fields and retention according to the actual audit purpose. Keep unrelated values out of long-lived logs.