code-review

To automate code review for a pull request, identify changed files and assess them against architecture, security, and quality rules. The workflow reads module conventions, applies mandatory CI/CD verification gates, and outputs a structured report flagging violations with fix suggestions.

A CI/CD verification gate in code review is a mandatory checkpoint enforcing generate, typecheck, test, and build steps before merge. It ensures code modifications pass standardized quality checks and build successfully, preventing unverified changes from entering the main branch.

To enforce architecture and security rules during code changes, evaluate modified files against module conventions defined in AGENTS.md and specs. The review process identifies violations, assigns severity levels, and provides targeted remediation guidance in a final report.

Yes, you can use this automated code review workflow for TypeScript projects. The mandatory CI/CD gate explicitly enforces typecheck and build steps, ensuring your TypeScript code adheres to defined architecture, security, and quality standards before merging.

To generate a code review report with fix suggestions, run the mandatory CI/CD gates after pushing your PR. The workflow evaluates changed files against established rules and outputs a structured report highlighting violations with precise remediation guidance.

The limitations of automated code review for CI/CD include its dependency on predefined AGENTS.md and specs to evaluate rules; without accurate module conventions, the workflow cannot effectively flag violations or provide reliable fix suggestions for your code changes.