validate-changes

To validate code changes against a design document, run a pre-review check that flags divergences from project conventions. This ensures proposed modifications meet project standards and align with the original design specifications before submission.

Checking for missing environment variables involves verifying that local config files and env vars are documented or updated. Pre-review validation enforces this documentation to prevent misalignments and environment-related regressions during local development.

Enforcing .gitignore hygiene requires checking that important files are ignored or updated as needed during development. Pre-review validation ensures your ignore lists are updated, preventing sensitive or unnecessary files from entering version control.

Yes, pre-review validation provides a quick pass/fail signal for code changes. This mechanism streamlines the review process by immediately indicating whether all checklist items, including design alignment and config updates, are satisfied.

You can use automated quality assurance to prevent regressions in your dev workflow by validating changes meet project standards before code review. This process checks environment configuration, .gitignore hygiene, and design document alignment.