gsd-code-review

To review changed source files from a specific development phase, you provide an explicit file list or summary-based scoping with a configurable review depth to target bugs, security vulnerabilities, and code quality problems without scanning the entire repository.

Severity classification in code review workflows surfaces issues with clear severity levels, allowing teams to quickly prioritize and remediate critical bugs and security vulnerabilities before they reach the next development step.

Yes, you can run iterative fix loops for bug detection and security review. The workflow supports optional fix or re-review loops, allowing developers to iteratively remediate findings and validate improvements.

The best way to scope a security review is through phase-based analysis using explicit file lists and summary-based scoping, ensuring the review targets only changed source files rather than blindly scanning an entire repository.

Yes, phase-based code review works without scanning the entire repository by applying explicit file scoping and summary-based inputs to analyze only the source files changed during a specified development phase.

Code quality problems may be missed without phase-scoped code review workflows that apply configurable review depth and structured findings with severity classification to catch bugs and security issues before they ship.