gsd-code-review

Identify changed files since main and generate a structured REVIEW.md with findings and severities.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-code-review-alo-exp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-code-review
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/gsd-code-review
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-code-review-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the code review process by analyzing changes for bugs, security issues, and maintainability, producing a clear REVIEW.md with actionable findings.

Core Features & Use Cases

  • Assess changed files for bugs, security issues, and quality gaps across languages and frameworks.
  • Generate a structured REVIEW.md report that includes findings, severities, and recommended fixes.
  • Use during pull requests, merges, and pre-commit checks to accelerate safe code delivery.

Quick Start

Provide a concise code review of the latest commit by listing changes, identifying high-priority findings, and generating a REVIEW.md report.

Frequently Asked Questions about gsd-code-review

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

FAQPage Schema
How do I automate code review for a pull request?

This Skill identifies changed files since a branch diverged from main, assessing them for bugs, security issues, and code quality to generate a structured REVIEW.md with actionable findings.

What is the best way to generate a report for bugs and security issues found in a diff?

Generating a bug and security report involves assessing changed files and producing a structured REVIEW.md that categorizes findings by severity—CRITICAL, MAJOR, or MINOR—with recommended fixes.

Can I run a pre-commit code quality check across different programming languages?

Yes, this code review process is applicable across software projects and languages, handling small to large diffs for pre-commit checks, merges, and pull requests.

How does automated bug detection classify the severity of findings?

Automated bug detection classifies findings using three severity levels: CRITICAL, MAJOR, and MINOR, which are documented alongside actionable recommendations in the generated REVIEW.md file.

Does automated security review work with large diffs in pre-merge checks?

Yes, automated security review handles small to large diffs for pre-merge checks by identifying changed files since the branch diverged from main and assessing them for security vulnerabilities and bugs.