skills.rest
hanzlahabib
hanzlahabibCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

rcode-review-adversarial-general

Review artifacts skeptically and produce a Markdown bullet list of concrete findings.

2|1|Updated Apr 10, 2026
Search Tags:#code review#spec review#critique#risk analysis#findings#adversarial review
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-review-adversarial-general
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rcode-review-adversarial-general
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/core/rcode-review-adversarial-general
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-review-adversarial-general

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you critically review an artifact and surface the flaws, omissions, and risks that a superficial pass would miss.

Core Features & Use Cases

  • Skeptical Review: Examines diffs, specs, stories, documents, and other artifacts with a deliberately adversarial mindset.
  • Gap Detection: Identifies missing requirements, weak assumptions, unclear behavior, and downstream risks before implementation or release.
  • Practical Use Case: Use it when you need a blunt, high-signal findings report that highlights concrete issues to fix next.

Quick Start

Ask the skill to adversarially review the provided artifact and return a Markdown bullet list of concrete findings.

Frequently Asked Questions about rcode-review-adversarial-general

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

FAQPage Schema
How do I run an adversarial review on a software spec or diff?▼

To run an adversarial review, provide your artifact like a diff or spec and request a skeptical findings report. The review applies an adversarial mindset to expose gaps, risks, and missing details before implementation.

What is an adversarial code review and when do I need it?▼

An adversarial code review is a skeptical evaluation that deliberately searches for flaws, omissions, and risks in an artifact. You need it when a superficial pass is insufficient and you must expose missing requirements before release.

How do I find gaps and missing requirements in a project story before shipping?▼

You find gaps by running an adversarial review on the project story. This process identifies missing requirements, weak assumptions, and unclear behavior, producing a blunt findings report of concrete issues to fix next.

What format does the adversarial review output use for reporting findings?▼

The review output uses a Markdown bullet list format. It requires at least ten concrete findings detailing gaps and risks, and includes halt conditions if the input is empty or the review appears suspiciously clean.

Can I use an adversarial review for documents other than source code diffs?▼

Yes, you can use it to review documents, specs, and stories. The review targets any artifact where gaps, risks, and missing details must be exposed, applying a deliberately skeptical mindset to surface flaws.

Related Skills

Explore More Software Engineering Skills→
josemariafsjosemariafs
3

bmad-review-adversarial-general

Identify issues in content through adversarial review and output a Markdown findings report.

Community
Advanced
Codagent-AICodagent-AI
30

review-assumptions

Audit implementor session reports for risky assumptions and context gaps.

Official
Advanced
zeronx798zeronx798

requesting-code-review

Scan staged git changes for security issues and quality regressions.

Community
Advanced
alangebalangeb

code-review-workflow

Run pyscan, pyanalyze, ruff, and black to generate a unified markdown report.

Community
Intermediate