gsd-code-review

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

Updated May 22, 2026

Search Tags:#diff analysis #code review #security review #bug detection #review automation #phase workflow

Ready to run

npx skills add https://github.com/yusaduymaz/loexai --skill gsd-code-review-yusaduymaz

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates structured reviews of phase-scoped source changes so you can catch bugs, security issues, and maintainability problems without manually inspecting every diff.

Core Features & Use Cases

Phase-aware review: Analyzes the changes associated with a specific phase and turns them into severity-classified findings.
Flexible scoping: Supports explicit file lists, summary-based scoping, and diff-based fallback when narrowing the review.
Optional remediation: Can drive a fix loop after review so teams can move from findings to patches faster.
Use case: Run it when a feature phase is complete and you need a concise, prioritized audit before merging.

Quick Start

Ask the skill to review phase 2 changes for bugs, security issues, and code quality problems.

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 phase-scoped source changes?▼

You can automate code review by running a phase-aware analysis on your repository changes, which generates severity-classified findings for bugs, security vulnerabilities, and code quality issues without manual diff inspection.

What is diff-based analysis and when do I need it for bug detection?▼

Diff-based analysis evaluates the exact lines changed in a source code update to identify bugs and security vulnerabilities. You need it when you want to review only the modified code in a targeted file scope rather than the entire repository.

How do I review specific files for security vulnerabilities and code quality issues?▼

You can review specific files by providing an explicit file list to scope the code review. The analysis then processes only those targeted files to detect security vulnerabilities and code quality problems.

Can I run a fix loop after a code review to patch identified bugs?▼

Yes, you can enable optional remediation to drive a fix loop after the code review. This allows your software delivery team to move from severity-classified findings to patches faster through review iteration support.

Does automated security review work without specifying explicit files?▼

Yes, the security review works without explicit files by using summary-based scoping or diff-based fallback. It resolves the review scope from phase context to ensure all relevant phase changes are still analyzed for risks.