contact715

Adversarial Self Review — Development skill for Claude Code

Development community

Skill: Adversarial self-review — try to break your own work before shipping.

How to install Adversarial Self Review

Installs to ~/.claude/skills/contact715-jidoka-adversarial-self-review/SKILL.md

Terminal
mkdir -p ~/.claude/skills/contact715-jidoka-adversarial-self-review && curl -fsSL https://raw.githubusercontent.com/contact715/jidoka/HEAD/.claude/skills/adversarial-self-review.md -o ~/.claude/skills/contact715-jidoka-adversarial-self-review/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Adversarial Self Review does

Skill: Adversarial self-review — try to break your own work before shipping

Wave: w28 | Status: experimental | Tags: [process, qa, falsification]


When to use

  • Before any commit that contains > 30 LOC of new code.
  • Before declaring a wave done.
  • Before responding "this is fixed" to a user.

The instinct after finishing a piece of work is to **verify** it (does it pass tests? does TS compile?). Verification finds known failure modes. Adversarial review finds **unknown** failu

Alternatives in Development

  • Om Tidy — Self-maintenance pass — acts on every hygiene flag: archives completed work, groups loose clusters, splits ove 4.6k ★
  • Defensive Code Cleanup — Clean Defensive Try-Catch Blocks 1.2k ★
  • AgentHandover — What if OpenClaw, Claude Code, Codex etc. knew how to do your work without you saying it 600 ★

Full documentation available on GitHub

View Source Repository