gsd-code-review

To review code changes for bugs and security vulnerabilities, you can run a code review on source files modified during a specific phase. This process analyzes the code at a chosen depth and generates a REVIEW.md artifact with severity-classified findings.

Yes, you can limit the scope of a code review to specific source files. By supplying the optional --files argument alongside the required phase number, the review agent restricts its analysis to only the specified files.

Code review depths control the analysis intensity applied to source files. You select from quick, standard, or deep levels to adjust how thoroughly the agent scans for code quality problems, bugs, and security vulnerabilities during the phase.

A phase-based code review classifies findings by severity and reports them in a REVIEW.md artifact. This markdown file is generated directly in the phase directory to summarize all detected bugs, security vulnerabilities, and quality issues.

To run an automated code review on phase changes, you need the specific phase number to scope the analysis. You can then optionally specify a depth level and file list to control the review's thoroughness and target scope.

You should use a deep code review instead of a quick scan when you need comprehensive analysis of source files for complex security vulnerabilities and bugs. If you only need a fast check of recent phase changes, the quick depth setting is more appropriate.