review-changes

To check code changes for CLI and VSCode extension drift before a commit, review your diff to verify event parity, type alignment, and YAML flow parsing stability. This validates that recent modifications have not broken synchronized event contracts across surfaces.

Cross-surface drift in CLI and VSCode extensions occurs when code changes desynchronize event contracts in the JSON emitter and extension bridge. Detecting this drift ensures type alignment and consistent behavior across both interfaces during code reviews.

To validate YAML flow parsing regressions when modifying code, analyze your code diff and run targeted tests to verify parsing stability. This process detects regressions introduced by changes and suggests concrete fixes to restore parser integrity.

Yes, you can use a diff review to detect JSON emitter contract breakage by checking for synchronized event contracts between the emitter and the extension bridge. This ensures type definitions remain up-to-date and aligned before deployment.

Yes, reviewing code changes requires up-to-date type definitions to validate the extension bridge and JSON emitter contracts. Synchronized type definitions are necessary to accurately analyze diffs and detect cross-surface drift or YAML parsing issues.

Automated code change reviews for YAML parsing are limited to detecting drift and regressions based on the current diff. They require synchronized event contracts and up-to-date type definitions to provide accurate fixes, and cannot validate untracked external dependencies.