gds-code-review

Reviews code changes with parallel adversarial review layers and structured triage.

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill gds-code-review-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-code-review
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/gds-code-review
Command: npx skills add https://github.com/PastaSus/egg-defender --skill gds-code-review-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss subtle bugs, edge cases, or deviations from the spec because a single reviewer pass lacks diverse perspectives. This Skill runs adversarial multi-layer reviews and triages findings into actionable categories so nothing slips through. ## Core Features & Use Cases - Parallel Review Layers: Launches three independent reviewers — Blind Hunter (diff-only), Edge Case Hunter (diff plus project access), and Acceptance Auditor (diff against spec) — to catch different classes of issues. - Structured Triage: Normalizes, deduplicates, and classifies findings into decision_needed, patch, defer, or dismiss buckets. - Actionable Outcomes: Writes findings into the story file, applies patches on request, tracks deferred work, and syncs sprint status. - Use Case: After finishing a story branch, ask for a review; the Skill gathers the diff, runs all review layers, presents triaged findings, and updates the story status to done or in-progress. ## Quick Start Ask the assistant to run a code review on your current branch changes against the story spec.

Frequently Asked Questions about gds-code-review

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

FAQPage Schema
How do I run an adversarial code review on my changes?

Trigger the review by saying "run code review" or "review this code". The workflow gathers your diff from staged changes, a branch diff, a commit range, or a pasted diff, then launches parallel review layers and triages the findings.

What review layers does this code review workflow use?

It uses three parallel layers: Blind Hunter reviews the diff with no project context, Edge Case Hunter reviews the diff with project read access, and Acceptance Auditor checks the diff against the spec and context docs when a spec file is provided.

Can I review code without a spec or story file?

Yes, the workflow supports a no-spec mode. The Acceptance Auditor layer is skipped, findings are still triaged and presented, but nothing is written to a story file and sprint status is not synced.

What happens if a review subagent fails or returns nothing?

The failed layer name is recorded and the review proceeds with findings from the remaining layers. If zero findings remain and any layer failed, the workflow warns that the review may be incomplete instead of declaring it clean.

How are code review findings classified and handled?

Findings are deduplicated and classified as decision_needed, patch, defer, or dismiss. Decision items require your input, patches can be applied automatically, deferred items go to a deferred-work file, and dismissed items are dropped.

Does the review update story status and sprint tracking?

Yes, when a spec file is set. The story status becomes done if all findings are resolved or in-progress if action items remain, and the matching entry in sprint-status.yaml is updated when a story key is available.