review-data-integrity

Review database transaction safety, ACID properties, and schema design quality.

12|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/wfukatsu/nexus-architect --skill review-data-integrity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-data-integrity
Source: https://github.com/wfukatsu/nexus-architect/tree/main/skills/review-data-integrity
Command: npx skills add https://github.com/wfukatsu/nexus-architect --skill review-data-integrity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill reviews the integrity of data, transaction safety, and schema design quality, providing a comprehensive assessment independent of ScalarDB.

Core Features & Use Cases

  • Transaction Safety Review: Evaluates the appropriateness of transaction boundaries and ACID property guarantees.
  • Data Consistency Check: Assesses the acceptable range for eventual consistency and conflict resolution strategies.
  • Schema Design Quality Analysis: Inspects normalization levels, index design, and migration safety.
  • Use Case: For projects not using ScalarDB, this Skill offers a perspective within a parallel review system to ensure robust data integrity.

Quick Start

Run the 'review-data-integrity' skill to start the data integrity review process.

Frequently Asked Questions about review-data-integrity

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

FAQPage Schema
How do I review database schema design and data consistency?

Data integrity reviews evaluate transaction boundaries, ACID property guarantees, eventual consistency, conflict resolution strategies, normalization levels, index design, and migration safety to ensure robust database systems.

How do I check if my transaction boundaries and ACID properties are appropriate?

Checking transaction boundaries and ACID properties involves evaluating their appropriateness within your database system to guarantee transaction safety. This ensures that data consistency is maintained during concurrent operations and system failures.

What is the best way to assess eventual consistency and conflict resolution strategies?

Assessing eventual consistency and conflict resolution requires determining the acceptable range for delayed updates and evaluating how conflicting data writes are resolved to maintain overall data consistency across distributed database systems.

Can I review database migration safety and index design independently?

You can review database migration safety and index design independently to inspect schema design quality. This analysis ensures that structural changes and query optimization strategies maintain data integrity without disrupting existing transaction boundaries.

What are the limitations of relying solely on normalization levels for schema design quality?

Relying solely on normalization levels limits schema design quality analysis by ignoring transaction boundaries, index design, and migration safety. A comprehensive data integrity review must also evaluate ACID properties and eventual consistency.