ln-652-transaction-correctness-auditor

To audit database transactions for missing intermediate commits, this Skill analyzes your transaction handling logic to detect gaps where commits are absent, returning findings with severity, location, and remediation recommendations to prevent data inconsistencies.

Identifying long-held transactions causing deadlocks involves examining transaction scopes for extended open periods. This Skill flags transactions remaining open too long, providing location details and effort estimates to optimize locking and prevent deadlocks.

Checking database rollback handling configuration requires verifying proper mechanisms exist for error scenarios. This Skill audits your transaction logic to ensure rollback handling is correctly implemented, returning severity-ranked findings and remediation steps for any missing or flawed mechanisms.

You can analyze transaction scope to determine if it is too wide or too narrow using this Skill. It evaluates transaction boundaries to identify overly broad or restrictive scopes, returning recommendations to optimize performance and reduce locking issues.

Detecting trigger and notify interactions within a transaction scope is done by examining how these database events interact with your transaction boundaries. This Skill analyzes these interactions and returns findings with severity and remediation recommendations.