ln-652-transaction-correctness-auditor

Name: ln-652-transaction-correctness-auditor
Availability: InStock
Author: dorrio

Audit database transactions for correctness and return severity-ranked remediation findings.

Updated Dec 11, 2025

Search Tags:#performance #rollback #database #data integrity #auditing #transactions

Ready to run

npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-652-transaction-correctness-auditor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-652-transaction-correctness-auditor
Source: https://github.com/dorrio/sorteo-app-generator/tree/main/.agent/skills/ln-652-transaction-correctness-auditor
Command: npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-652-transaction-correctness-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and rectifies common issues in database transaction handling, ensuring data integrity and application stability.

Core Features & Use Cases

Intermediate Commit Checks: Detects missing commits that can lead to data inconsistencies.
Transaction Scope Analysis: Identifies transactions that are too broad or too narrow, optimizing performance and reducing locking issues.
Rollback Handling: Ensures proper rollback mechanisms are in place for error scenarios.
Long-Held Transaction Detection: Flags transactions that remain open for extended periods, preventing deadlocks.
Trigger/Notify Interaction: Analyzes interactions with triggers and notifications within transaction scopes.

Quick Start

Use the ln-652-transaction-correctness-auditor skill to audit the current transaction handling logic.

Frequently Asked Questions about ln-652-transaction-correctness-auditor

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

FAQPage Schema

How do I audit database transactions for missing intermediate commits?▼

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.

What is the best way to identify long-held transactions causing deadlocks?▼

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.

How do I check if my database rollback handling is configured correctly?▼

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.

Can I analyze transaction scope to see if it is too wide or too narrow?▼

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.

How do I detect trigger and notify interactions within a transaction scope?▼

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.