gsd-review

Automates code review of changed files and writes a PASS/BLOCK report.

6|3|Updated Mar 31, 2026

Search Tags:#security #quality #code-review #review-gate #changed-files #review-output

Ready to run

npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-review-alo-exp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-review
Source: https://github.com/alo-exp/silver-bullet/tree/main/skills/gsd-review
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-review-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the review of changed files to identify bugs, security issues, and quality gaps, and to generate a structured REVIEW.md for governance before merging.

Core Features & Use Cases

Changed-file enumeration: Detects files touched in a branch and groups them by module or concern.
Quality and security checks: Flags bugs, potential security issues, and maintainability concerns per file.
Review gate & reporting: Classifies findings as CRITICAL, MAJOR, or MINOR and writes a REVIEW.md with a PASS/BLOCK gate to guide merges.

Quick Start

Use this skill to review a feature branch and produce a REVIEW.md before opening a pull request.

Frequently Asked Questions about gsd-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate code review for changed files in a feature branch?▼

Automated code review for changed files analyzes branches to detect bugs, security issues, and quality gaps before merging. It enumerates modified files, groups them by concern, and classifies findings by severity to produce a structured governance report.

What is a review gate and how does it guide pull request merges?▼

A review gate evaluates classified findings and outputs a PASS or BLOCK status in a REVIEW.md file. This gate guides merges by explicitly indicating whether critical or major defects must be resolved before the branch can be safely integrated.

How do I generate a REVIEW.md report for governance before opening a pull request?▼

To generate a REVIEW.md report, execute an end-to-end workflow that analyzes changed files for compliance and defects. The process writes a structured REVIEW.md containing severity classifications and a PASS or BLOCK merge gate.

Can automated code review detect security issues and maintainability concerns per file?▼

Yes, automated code review flags potential security vulnerabilities and maintainability concerns on a per-file basis. It inspects each changed file to surface compliance gaps and defects before generating the final review report.

How are code review findings classified by severity during the analysis?▼

Code review findings are classified by severity as CRITICAL, MAJOR, or MINOR. This severity classification helps prioritize bug resolution and quality improvements based on the impact and risk level of the detected issues.