skills.rest
MazenMrad
MazenMradCOMMUNITY
Explore all skills by this author →
GitHub

gds-code-review

Automates parallel adversarial code reviews to triage findings from diffs or PRs.

1|Updated Aug 3, 2025
Search Tags:#context#diff#spec#triage#code-review#adversarial
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill gds-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-code-review
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/gds-code-review
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill gds-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial code reviews help teams quickly surface critical issues in code changes by applying multi-layer scrutiny that reduces bias and increases reliability.

Core Features & Use Cases

  • Parallel review layers: Blind Hunter, Edge Case Hunter, and Acceptance Auditor coordinate to triage findings into actionable categories.
  • Structured triage: auto-normalizes findings into a consistent format for fast decision-making.
  • Works with diffs or PR changes: integrates with standard code review workflows to accelerate quality gates.

Quick Start

Submit a diff or PR reference to trigger parallel adversarial reviews and triage.

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 reviews for PR diffs?▼

Automate adversarial code reviews by submitting structured PR diffs to trigger parallel critique layers, which surface actionable findings through Blind Hunter, Edge Case Hunter, and Acceptance Auditor for targeted triage.

What is adversarial code review and how does multi-layer scrutiny work?▼

Adversarial code review applies multi-layer scrutiny to code changes, reducing bias and increasing reliability by running parallel critique layers like Blind Hunter and Edge Case Hunter to surface critical issues.

Can I use structured diffs with optional spec docs for code review triage?▼

Structured diffs work with optional spec and context docs to provide narrative during code review triage, auto-normalizing findings into a consistent format for fast decision-making across projects.

What is the best way to triage code review findings into actionable categories?▼

Triage code review findings into actionable categories by applying parallel adversarial review layers that auto-normalize results, guiding targeted decision-making for quality gates in standard workflows.

Do I need structured diff inputs to run an automated code review?▼

Structured diff inputs are required to run automated code reviews, while optional spec and context documents provide additional project narrative to improve the accuracy of triage findings.

Related Skills

Explore More Software Engineering Skills→
enigmaicon-engenigmaicon-eng
1

bmad-code-review

Review code diffs with parallel adversarial layers and triage findings into actionable categories.

Community
Advanced
PrefectHQPrefectHQ
27.1k

review-issue

Triage external GitHub issues and gate-enabled PRs to assign or decline.

Official
Advanced
meistro57meistro57
1

laravel:quality-checks

Run automated quality gates for Laravel projects with Pint, PHPStan, and frontend linters.

Community
Intermediate
dwoolworthdwoolworth
1

code-review

Analyze pull request code changes and return PASS or FAIL with feedback.

Community
Advanced