cdk-review

To automate CDK code reviews, run the reviewer at your project root to validate App/Stack/Construct structure, type safety, naming conventions, and L2 construct usage. This generates a quality report highlighting infrastructure issues.

AWS CDK best practices include using L2 constructs, enforcing type safety, standardizing naming conventions, and applying appropriate removal policies. Automating these checks ensures consistency and reduces human error across large infrastructure deployments.

Yes, you can automatically check CDK App and Stack structure before refactoring. The reviewer validates your Construct hierarchy, Parameter classification, and import order to identify potential design issues and ensure code quality.

Automated CDK code review currently applies exclusively to TypeScript CDK projects. It validates TypeScript-specific patterns, type safety, and import ordering, making it unsuitable for Python, Java, or other CDK language bindings.

Using L2 constructs in AWS CDK provides built-in defaults, better type safety, and simplified syntax compared to L1 constructs. Automated reviews check for L2 construct usage to ensure your infrastructure follows best practices and reduces boilerplate.