code-review

Automated static analysis scans changed source files to identify security vulnerabilities, bugs, and style violations. It applies deterministic analysis and severity classification to generate a structured REVIEW.md report with actionable remediation steps.

Generating a structured code review report for merge gates involves scanning source files for maintainability risks and defects. The process outputs a standardized REVIEW.md with findings organized by critical, warning, and info severity levels for triage.

Severity classification for bugs and security risks works by categorizing every finding into critical, warning, or info levels during static analysis. This allows maintainers to triage defects efficiently and provides clear next steps and owners for remediation.

You can scan specific file paths for maintainability concerns and style violations. The static analysis targets source files changed during a phase or within specified paths to identify defects and produce a concise summary of findings.

No external dependencies are required to run an automated code-quality review. The static analysis operates independently to identify defects, security vulnerabilities, and maintainability risks, directly outputting the REVIEW.md report.

A structured remediation handoff is needed when teams require clear next steps and accountability for resolving identified bugs and security vulnerabilities. It enables faster resolution by assigning owners to each finding in the REVIEW.md report.