Ln 652 Transaction Correctness Auditor

What it does

This skill, the Ln 652 Transaction Correctness Auditor, is a specialized AI worker designed to audit database transaction patterns for correctness and consistency. It checks commit patterns, transaction boundaries, rollback handling, and trigger/notify semantics within a codebase. The auditor produces structured findings detailing severity, location, effort required for remediation, and recommendations, alongside calculating a compliance score (out of 10) for the "Transaction Correctness" category.

When to use it

• When performing code reviews for database-driven applications.
• To proactively identify potential errors or inconsistencies in transaction logic before deployment.
• During security audits to ensure proper handling of database transactions and triggers.

Key capabilities

• Audits transaction correctness, scope, and trigger interaction.
• Checks commit patterns, transaction boundaries, rollback handling, and trigger/notify semantics.
• Generates structured findings with severity levels, location details, effort estimates, and remediation recommendations.
• Calculates a compliance score (X/10) for Transaction Correctness.
• Supports domain-aware analysis using domain_mode and current_domain.
• Requires loading shared/references/audit_worker_core_contract.md and shared/references/two_layer_detection.md.

Example prompts

• "Audit the transaction logic in this codebase for correctness."
• "Check the commit patterns and rollback handling within these migration files."
• "Analyze trigger-affected tables and their associated UPDATE paths."

Tips & gotchas

• Mandatory Read: The skill requires loading shared/references/audit_worker_core_contract.md and shared/references/two_layer_detection.md to function correctly. Failure to load these will result in inaccurate or incomplete results.
• The skill is a Level 3 (L3) worker, indicating it's designed for more specialized tasks.