gsd-code-review

Code review for phase-scoped changes targets bugs, security vulnerabilities, and quality problems by analyzing only the files modified during that phase. It catches regressions before they spread without manually combing through the entire repository.

Phase-based code review analyzes files changed during a specific development phase rather than the whole codebase. It is needed when you want to catch bugs and security issues early in a phased workflow before they propagate further.

Yes, you can provide an explicit file list for deterministic scoping to review exactly the files you care about. This ensures the code review focuses only on those specified files for bugs and security vulnerabilities.

Quick, standard, and deep code review passes offer flexible depth control depending on how much scrutiny the change requires. Choose quick for fast checks, standard for typical changes, and deep for thorough bug detection and security analysis.

An automated code review report produces a REVIEW.md artifact in the phase directory with severity-classified findings. It also generates an inline summary for workflow follow-up to track identified bugs and security vulnerabilities.

Workflow automation for code review requires no external dependencies. It operates independently to analyze phase-scoped source files, classify findings by severity, and generate review reports within your existing phase-based workflow.