gsd-code-review

Automated code review analyzes your Git diff to detect security vulnerabilities, bugs, and quality issues. It performs a phase-based assessment of changed source files and produces a structured REVIEW.md artifact with severity-classified findings for traceability.

Scoping code quality analysis to specific files is supported via an optional file list input. This targets the review checks toward selected changed files rather than the entire phase, allowing for faster and more focused automated security and quality assessments.

You can control code review depth using quick, standard, or deep analysis modes. Depth control allows you to balance the speed of the automated review against the thoroughness of bug, security vulnerability, and quality issue detection for your phase changes.

Automated phase-based code review applies to workflows where a Git diff or phase artifacts are available. It requires a phase-number input to identify the changes and generates a REVIEW.md artifact directly in the corresponding phase directory for traceability.

Generating a REVIEW.md artifact for code changes provides a persistent, structured assessment with severity-classified findings. This ensures traceability of detected bugs, security vulnerabilities, and quality issues within the phase directory, unlike transient inline comments.

Yes, automated code review supports phase-based work where phase artifacts are available even without a direct Git diff. It analyzes these artifacts to surface defects, security issues, and quality gaps, outputting a structured REVIEW.md with classified findings.