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.