gsd-code-review

To find bugs and security vulnerabilities before merge, you can use an automated code review process that analyzes changed files in a specific phase. This Skill spawns a code-reviewer agent to identify security issues and quality problems, outputting a severity-classified findings artifact.

Yes, you can control the depth of static analysis during a pre-merge code review by configuring the review mode. The Skill supports quick, standard, and deep review depths, allowing you to balance scanning speed against thorough cross-file reasoning.

The best way to automate patch remediation is to spawn an automated fixer workflow after identifying security findings. This workflow applies suggested changes to the source files and can optionally re-review the code iteratively to verify the remediation.

Yes, this code review approach works for multiple programming languages. The analysis applies to file sets changed during a specified review phase, supporting security-minded software engineering workflows across diverse codebases without language-specific limitations.

Code review findings for tracking patch validation are formatted as a padded phase-REVIEW.md artifact. This output file contains severity-classified findings and an inline summary, providing actionable next steps for your software engineering workflow.