Database Deadlock Detector Skill for Lock Ordering
Read a PostgreSQL deadlock log, map held and requested resources, and check whether code paths acquire locks consistently.
中文Install in Claude Code
Use your local test database or synthetic logs. The example starts from two fictional transactions.
- Get the complete `plugins/database/database-deadlock-detector/skills/detecting-database-deadlocks` directory from the pinned GitHub commit.
- Copy it into the target project's `.claude/skills/`. Check `.claude/skills/detecting-database-deadlocks/SKILL.md`, start Claude Code at the project root, and call `/detecting-database-deadlocks`.
Example task
Model A holding row 1 while waiting for row 2, and B holding row 2 while waiting for row 1. Draw both wait edges and propose updating rows in ascending ID order.What to check
The report identifies the A–B cycle and explains how consistent ordering removes that cycle in the example.
Original SKILL.md on GitHub · Updated
Frequently asked question
Does any lock wait indicate a deadlock?
Check for a cycle. A one-way wait can clear when the other transaction completes.