ln-652-transaction-correctness-auditor

Audit database transaction patterns for scope, rollback, and trigger interactions.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-652-transaction-correctness-auditor-cbbkrd-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-652-transaction-correctness-auditor
Source: https://github.com/cbbkrd-tech/jl-finishes/tree/main/.claude/skills/ln-652-transaction-correctness-auditor
Command: npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-652-transaction-correctness-auditor-cbbkrd-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and reports on critical issues in database transaction handling, preventing data corruption, performance degradation, and application instability.

Core Features & Use Cases

  • Transaction Auditing: Analyzes transaction scope, commit patterns, rollback handling, and trigger interactions.
  • Violation Detection: Identifies missing intermediate commits, overly wide or narrow transaction scopes, and improper rollback procedures.
  • Use Case: A developer can use this Skill to automatically scan their codebase for common transaction pitfalls, ensuring data integrity and preventing issues like deadlocks or inconsistent states before they impact production.

Quick Start

Run the ln-652-transaction-correctness-auditor skill to audit the codebase located at /path/to/codebase.

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 my codebase for database transaction correctness issues?

Database transaction auditing analyzes transaction scope, commit patterns, rollback handling, and trigger interactions. It detects missing intermediate commits, overly wide or narrow transaction scopes, and improper rollback procedures to prevent data corruption and application instability.

Why does my application experience data corruption or deadlocks during database transactions?

Database transaction auditing analyzes transaction scope, commit patterns, rollback handling, and trigger interactions. It detects missing intermediate commits, overly wide or narrow transaction scopes, and improper rollback procedures to prevent data corruption and application instability.

What is the best way to detect missing rollback handling in database transactions?

Database transaction auditing analyzes transaction scope, commit patterns, rollback handling, and trigger interactions. It detects missing intermediate commits, overly wide or narrow transaction scopes, and improper rollback procedures to prevent data corruption and application instability.

Can I check my codebase for long-held transactions and trigger interaction problems?

Database transaction auditing analyzes transaction scope, commit patterns, rollback handling, and trigger interactions. It detects missing intermediate commits, overly wide or narrow transaction scopes, and improper rollback procedures to prevent data corruption and application instability.

Does transaction auditing work for analyzing overly wide or narrow transaction scopes?

Database transaction auditing analyzes transaction scope, commit patterns, rollback handling, and trigger interactions. It detects missing intermediate commits, overly wide or narrow transaction scopes, and improper rollback procedures to prevent data corruption and application instability.