review-correctness-state-schema-transaction

Review pull request diffs for state, schema, and transaction correctness flaws.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/D3Hunter/ai-engineer --skill review-correctness-state-schema-transaction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-correctness-state-schema-transaction
Source: https://github.com/D3Hunter/ai-engineer/tree/main/skills/review-correctness-state-schema-transaction
Command: npx skills add https://github.com/D3Hunter/ai-engineer --skill review-correctness-state-schema-transaction

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the risk of merging pull requests with undetected state-oriented correctness flaws that can lead to data corruption, broken transaction guarantees, or silent state regressions in production systems.

Core Features & Use Cases

  • Static Analysis-First Workflow: Reviews PR diffs for state, schema, and transaction issues without executing build or test commands, minimizing review latency and avoiding unintended side effects.
  • Comprehensive Correctness Coverage: Runs a mandatory checklist spanning state/data integrity, DDL/index semantics, transaction atomicity/isolation, numerical/time/locale correctness, and state-preservation regression traps.
  • Edge Case Boundary Validation: Performs mandatory cross-function state-machine traces and chunked ingestion boundary checks to catch rare but high-impact flaws like split record handling or delimiter misclassification.
  • Real-World Use Case: A PR modifying database migration logic or stateful log parser chunking can be reviewed to identify partial update inconsistencies or silent record drops that would cause data loss post-merge.

Quick Start

Use the review-correctness-state-schema-transaction skill to review the provided pull request diff for state, schema, and transaction correctness issues, then output all findings to the designated results file.

Frequently Asked Questions about review-correctness-state-schema-transaction

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

FAQPage Schema
How do I review a pull request for state and transaction correctness flaws?

Reviewing pull requests for state and transaction correctness involves applying static analysis to the PR diff to identify data corruption risks, broken transaction atomicity, and silent state regressions without executing build or test commands.

What is static analysis for schema validation in code review?

Static analysis for schema validation in code review is the process of examining PR diffs for DDL and index modifications to prevent data corruption and ensure state integrity before merging changes into production systems.

How do I catch chunked ingestion boundary issues in a stateful log parser?

To catch chunked ingestion boundary issues in a stateful log parser, perform cross-function state-machine traces and boundary validation to identify split record handling errors or delimiter misclassification that cause silent data loss.

Does static code review work for database migration logic without running tests?

Yes, static code review works for database migration logic without running tests by analyzing PR diffs against a mandatory correctness checklist to identify partial update inconsistencies and transaction isolation issues pre-merge.

When do I need cross-function state-machine tracing for pull request review?

You need cross-function state-machine tracing for pull request review when changes involve state mutations, numerical or time data handling, and chunked ingestion paths to catch rare but high-impact flaws like silent record drops.