sync-docs

To check if documentation matches the codebase after schema modifications, validate the consistency between specification documents and actual code. This detects omissions by matching table names, column names, FK relations, and Server Action signatures.

The best way to detect outdated data model specifications is to run a consistency check against your codebase. This identifies mismatches in table names, column names, UNIQUE constraints, and Server Action signatures to catch documentation update omissions.

You should validate specification and code consistency for Server Actions after implementation, renaming, or schema modifications. Running this check before committing ensures all related documentation in your project accurately reflects the code changes.

Yes, you can verify foreign key relations and unique constraints against specification documents. The consistency check requires precise matching of table and column names, FK relations, UNIQUE constraints, and Server Action signatures to detect discrepancies.

Yes, the documentation consistency check works without external dependencies. It operates using internal scripts and references to validate that your project documentation stays perfectly aligned with the codebase.

Project documentation shows mismatches after renaming data models because implementation, renaming, or schema changes create discrepancies between specifications and actual code. Running a consistency check detects these documentation update omissions.