gds-code-review

Coordinate parallel code review roles and triage findings into actionable categories.

Updated Nov 6, 2025
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill gds-code-review-skyoxu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-code-review
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/gds-code-review
Command: npx skills add https://github.com/skyoxu/godotgame --skill gds-code-review-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial, structured code review workflow that surfaces precise findings across multiple review perspectives and consolidates them into actionable items for developers.

Core Features & Use Cases

  • Parallel review layers: Blind Hunter, Edge Case Hunter, and Acceptance Auditor run concurrently to increase coverage and objectivity.
  • Structured triage: Findings are normalized, deduplicated, and categorized into patch, decision_needed, defer, or dismiss for fast remediation.
  • Context-aware reviewing: Accepts optional spec or context documents and updates a story or task with review outcomes.
  • Automation-ready outputs: Generates review findings suitable for integration into project boards and sprint planning.

Quick Start

Trigger the gds-code-review workflow on a code change and follow the prompts to run parallel reviews and triage findings.

Frequently Asked Questions about gds-code-review

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

FAQPage Schema
How do I automate adversarial code review to find edge cases in software engineering?

Adversarial code review automates issue detection by running parallel subagents like the Edge Case Hunter to concurrently analyze changes and surface objective findings for developer triage.

What is the best way to triage code review findings for sprint planning?

Triage code review findings by normalizing and deduplicating parallel review results into actionable categories like patch, decision_needed, defer, or dismiss for fast sprint integration.

How does parallel code review work with multiple subagents?

Parallel code review works by coordinating concurrent roles—Blind Hunter, Edge Case Hunter, and Acceptance Auditor—to increase coverage, objectivity, and consolidate structured findings.

Can I include project context and specs when running an automated code review?

Yes, automated code review accepts optional spec or context documents to perform context-aware reviewing, updating your story or task with structured review outcomes.

What are the limitations of using parallel subagents for code review?

Parallel subagent code review requires a structured workflow of context loading and result consolidation, meaning it outputs triaged findings and remediation plans rather than applying patches directly.