gsd-code-review

To automate phase-based code review, you provide a phase number and optional depth to analyze changed files for bugs, security, and quality issues. It generates a REVIEW.md artifact with a severity-classified findings summary and actionable recommendations.

Code review depth options control the analysis intensity applied to changed files. Quick, standard, and deep depths allow you to scale the scrutiny of bugs and security vulnerabilities based on your phase requirements and available review time.

You can scope code reviews to specific files using the optional --files override. When provided, this filter targets only the specified files and skips further phase-based scope resolution across repositories.

Generating a markdown report for security and code quality findings is done by running a phase review. The process outputs a {phase}-REVIEW.md artifact containing an inline summary of severity-classified findings and actionable recommendations.

Phase-based code review enforces phase validation and gating to ensure reviews run against a valid phase state. This mechanism prevents analyzing code changes when the underlying phase state is invalid or incomplete.