reviewer

To validate CDK stack changes against project patterns, you can use an automated code review process that analyzes your infrastructure code diff for adherence to multi-stack architecture, documentation, and coding standards. This prevents inconsistencies before merging.

Infrastructure code review checks CI/CD workflow configurations for security best practices like OIDC usage and the inclusion of verification stages. It ensures pipeline configurations align with established project patterns and security standards.

Yes, you can check if critical documentation like HISTORY.md is updated alongside code changes through automated documentation verification. This flags missing documentation updates, ensuring infrastructure modifications are properly recorded.

Yes, the reviewer skill requires read access to project files for comparing code diffs against established patterns and documentation. This access is necessary to analyze infrastructure changes and identify deviations from project standards.

The best way to ensure consistency in multi-stack CDK architecture modifications is to apply automated validation against established project patterns. This approach analyzes proposed changes to flag deviations from coding standards and architectural best practices.

You should validate infrastructure changes before merging a pull request to prevent inconsistencies and maintain code quality. Validating changes ensures adherence to established project patterns, best practices, and documentation standards.