gsd-code-review

Review phase-changed source files for bugs, security vulnerabilities, and quality issues.

264|11|Updated Apr 25, 2026

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

Ready to run

npx skills add https://github.com/coco-research/coco --skill gsd-code-review-coco-research

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review phase-scoped code changes without manually combing through every file, so bugs, security issues, and quality regressions are caught before they spread.

Core Features & Use Cases

Phase-Based Review: Analyze the files changed in a specific phase rather than the entire repository.
Flexible Depth Control: Choose quick, standard, or deep review passes depending on how much scrutiny the change requires.
Deterministic Scoping: Provide an explicit file list when you need to review exactly the files you care about.
Actionable Output: Produces a REVIEW.md artifact with severity-classified findings and an inline summary for workflow follow-up.

Quick Start

Ask the skill to review phase 2 at standard depth, or give it an explicit file list when you want deterministic scoping.

Frequently Asked Questions about gsd-code-review

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

FAQPage Schema

How do I review code changes for bugs and security vulnerabilities in a specific development phase?▼

Code review for phase-scoped changes targets bugs, security vulnerabilities, and quality problems by analyzing only the files modified during that phase. It catches regressions before they spread without manually combing through the entire repository.

What is phase-based code review and when do I need it?▼

Phase-based code review analyzes files changed during a specific development phase rather than the whole codebase. It is needed when you want to catch bugs and security issues early in a phased workflow before they propagate further.

Can I scope code review to an explicit file list for deterministic results?▼

Yes, you can provide an explicit file list for deterministic scoping to review exactly the files you care about. This ensures the code review focuses only on those specified files for bugs and security vulnerabilities.

How do I choose between quick, standard, and deep code review passes?▼

Quick, standard, and deep code review passes offer flexible depth control depending on how much scrutiny the change requires. Choose quick for fast checks, standard for typical changes, and deep for thorough bug detection and security analysis.

What output format does an automated code review report use?▼

An automated code review report produces a REVIEW.md artifact in the phase directory with severity-classified findings. It also generates an inline summary for workflow follow-up to track identified bugs and security vulnerabilities.

Does workflow automation for code review require any external dependencies?▼

Workflow automation for code review requires no external dependencies. It operates independently to analyze phase-scoped source files, classify findings by severity, and generate review reports within your existing phase-based workflow.