gsd-code-review

Name: gsd-code-review
Availability: InStock
Author: lgwanai

Review phase-scoped source changes for bugs, vulnerabilities, and quality issues.

4|1|Updated Mar 22, 2026

Search Tags:#static analysis #code review #security #DAG workflow #phase-based changes #fix and re-review

Ready to run

npx skills add https://github.com/lgwanai/openforce --skill gsd-code-review-lgwanai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-code-review
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-code-review
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-code-review-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly review the source files changed in a given phase to find bugs, security vulnerabilities, and code quality problems before they merge.

Core Features & Use Cases

Phase-scoped code review: Reviews the changes associated with a specified phase number.
Configurable review depth: Supports quick pattern-matching, standard per-file analysis, and deep cross-file analysis (import graphs and call chains).
Precise scoping controls: Uses phase scoping by default, or switches to an explicit file list when provided.
Optional automated fixes: Can apply fixes via a dedicated fixer workflow and re-review iteratively.
Output as a review artifact: Produces a phase directory artifact named with the padded phase number and inlined severity-classified findings.

Quick Start

Run gsd-code-review for phase 2 with standard depth: "openforce /gsd-code-review 2 --depth=standard".

Frequently Asked Questions about gsd-code-review

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

FAQPage Schema

How do I perform a code review scoped to a specific development phase?▼

Phase-scoped code review targets bugs and security vulnerabilities in source files changed within a specified phase. You specify a phase number to isolate the review and generate a padded_phase-REVIEW.md artifact with classified findings.

What is the difference between quick, standard, and deep code analysis depths?▼

Code analysis depths include quick pattern-matching, standard per-file analysis, and deep cross-file analysis. Deep analysis uses import graphs and call chains to identify bugs and security vulnerabilities across files.

Can I apply automated fixes and re-review code changes iteratively?▼

You can apply automated fixes via a dedicated fixer workflow and re-review code changes iteratively. This resolves identified bugs and security vulnerabilities before generating the final severity-classified review artifact.

How do I review an explicit list of changed files instead of a phase number?▼

Provide an explicit file list to switch from default phase scoping to reviewing specific source files. This ensures the code review targets only the specified files to identify bugs and security vulnerabilities.

What artifact format does phase-based static analysis generate for code review findings?▼

Phase-based static analysis generates a padded_phase-REVIEW.md artifact in a phase directory. This artifact contains severity-classified findings for identified bugs, security vulnerabilities, and code quality issues.