adversarial-review
Skill7 starsChanged 5 months agoMITView on GitHub
敵対的分析手法を統合したレビューの entry skill。認知バイアス対策の3手法 (Pre-mortem / War Game / Logic Torturing)と、宣言・主張と実態の乖離を突く claim-vs-actual 検出3パターン(Self-Contradiction / Refactor-Claim Audit / Cross-File Leakage)へルーティングし、通常のレビューでは見えない設計の盲点・ 防御の穴・論理の弱点・宣言と実装のズレを可視化する。
111 other projects use a version of this.
Adopted by
Most recently taken up by
- moiz-73/glassboxtheir own version, first seen Nov 16, 2026
- Alexpechonov/claude-skillstheir own version, first seen Nov 16, 2026
- anton-abyzov/specwithcodetheir own version, first seen Nov 16, 2026
- Axect/skillstheir own version, first seen Nov 16, 2026
- magnusrodseth/dotfilestheir own version, first seen Nov 16, 2026
- lennoxsaint/Skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use rethink, root-cause-analysis and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
fabioespindulaSkillrethink
Reframe a plan, idea, or decision before the user commits to it. Use when the user asks to rethink, step back, pressure-test, gut-check, decide, right-size, simplify, think bigger about, or evaluate a concrete plan or decision in product, strategy, technical architecture, career, life, company direction, or personal priorities. This skill improves decision quality before action: clarify the real question, challenge assumptions, compare alternatives, calibrate ambition, classify the operating mode, surface risks, and recommend a next move. Do not use for broad future exploration without a concrete decision; that belongs to a think-big or research-style skill.
Also in 3 projects that use this
MicrosoftSkillroot-cause-analysis
Use when a Regional Retail Manager asks I'm seeing unusual inventory movement at our Northwest stores. Can you help me understand what's happening?
Also in 3 projects that use this
anasahmed07Skillbetter-auth-best-practices
Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.
Also in 4 projects that use this
DockerSkillfix-issue
Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR. Use when asked to fix an issue: "fix issue 1234", "resolve #500", "create a PR for issue 200".
Also in 3 projects that use this
MicrosoftSkillpull-request
Write concise, focused pull request descriptions for Wassette — at most three sentences on the what and why, with an explicit note on any breaking public-API change and how users adapt. Use when opening or editing a Wassette pull request.
Also in 3 projects that use this
juriwiensSkillcodex-review
Run code review via Codex CLI
Also in 3 projects that use this
- +2 more from microsoft
Other versions111 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 111
- PrefectHQ/fastmcp★ 29ksame name
- jlowin/fastmcp★ 29ksame name
- mengxi-ream/read-frog★ 10ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
- basicmachines-co/basic-memory★ 4.6ksame name
- DanMcInerney/architect-loop★ 626same name
- deadlock-mod-manager/deadlock-mod-manager★ 617same name
- boraoztunc/skills★ 473same name
- syahiidkamil/Software-Engineer-AI-Agent-Atlas★ 404same name
101 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository140 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- static/llms.txtllms.txt
- ask-codexSkill
- river-review-disciplineSkill
- skill-creatorSkill
- skill-ops-plannerSkill
- skill-optimizerSkill
- commandsSkill
- review-teamSkill
- river-review-architectureSkill
- river-review-codeSkill
- river-review-docsSkill
- river-review-frontendSkill
- river-review-performanceSkill
- river-review-security-auditSkill
- river-review-securitySkill
- river-reviewSkill
- river-review-testingSkill
- unknown-coverage-reviewSkill
- Coverage and Failure Path GapsSkill
- Flaky Test Risk CheckSkill
- GitHub Actions Workflow Security ReviewSkill
- Standard Review Policy for DownstreamSkill
- Test Assertion Effectiveness 常に PASS するテストの検出Skill
- Test Presence for Changed CodeSkill
- Test Naming and StructureSkill
- テスト観点レビュー(差分ドリブン)Skill
- a11y Accessible Name BasicsSkill
- Agent Skill Bridge ReviewSkill
- Altitude Generalization GuardSkill
- API Compatibility and Test Gap ReviewSkill
- Assumption Resolution Trace Plan の前提解消トレーサビリティSkill
- Async Correctness 非同期処理の正しさ検証Skill
- Behavior-Structure Separation 振る舞い変更と構造変更の分離・外部挙動維持Skill
- Closure Scope Retention GuardSkill
- Component Variants / States Documentation コンポーネント状態の文書化Skill
- Configuration File ReviewSkill
- Cross-File Leakage リファクタ後の caller 側残骸検出Skill
- Design Source-of-Truth Conformance デザイン定義準拠Skill
- Design System Component Reuse GuardSkill
- Design Token EnforcementSkill
- Detector Detection Power 検査器の検出力の検証Skill
- Documentation Hygiene ドキュメント衛生Skill
- End-to-End Wiring 末端到達・貫通の検証Skill
- Existing-Pattern Conformance 既存パターン準拠の確認Skill
- Firebase Security Rules ReviewSkill
- Fix Scope Integrity 指摘対応ループのスコープ逸脱・前提破壊検出Skill
- GitHubレビューコメント対応(修正案つき)Skill
- Hallucinated Reference 幻覚的参照の実在確認Skill
- Hello Skill (Always-On Sample)Skill
- i18n Unused Key ReviewSkill
- Impact Evidence Coverage 影響・失敗系・外部依存の証拠充足Skill
- Independent Review SynthesisSkill
- Invisible Unicode Injection Scan 不可視 Unicode コード注入検出Skill
- Knowledge-to-Code Alignment 新知識のコード反映・設計知識の保全Skill
- Laravel Eloquent N+1 and Query Efficiency ReviewSkill
- Laravel Mass Assignment and Authorization ReviewSkill
- The first 60 shown.
The file
Files
Adversarial Review(敵対的レビュー)
通常のコードレビューは「正しさの確認」に集中する。 敵対的レビューは 「どう壊れるか」「どう攻撃されるか」「どこが論理的に弱いか」 に集中する。
背景 / Background
AIをレビューに使う最大の価値は、情報の整理ではなく 思考の死角を映す鏡 としての活用にある。 このスキルは、2系統の敵対的手法を体系化し、レビューの質を根本的に引き上げる。
認知バイアス対策(思考の死角)
| 手法 | 対策するバイアス | 核心の問い |
| Pre-mortem | 生存バイアス・楽観バイアス | 「失敗したとして、なぜ?」 |
| War Game | 自己中心バイアス | 「敵の立場から、どう攻撃する?」 |
| Logic Torturing | 確証バイアス | 「この論理の穴を潰して」 |
claim-vs-actual 検出(宣言・主張と実態の乖離)
| 手法 | 対象とするズレ | 核心の問い |
| Self-Contradiction | 宣言と同一ファイルの実装 | 「規則 X を宣言した本人が破っていない?」 |
| Refactor-Claim Audit | 完了主張と残骸 | 「『全部やった』を grep で反証できる?」 |
| Cross-File Leakage | 構造変更と caller 側 | 「直したのは変更元だけ、参照元は?」 |
When to Use / いつ使うか
- 設計判断やアーキテクチャ変更を含むPRのレビュー時
- セキュリティに影響する変更のレビュー時
- 重要な技術選択の妥当性を検証したいとき
- 「本当にこれで大丈夫か?」という不安があるとき
Routing / ルーティング
入力に応じて、適切な手法へルーティングする。複数手法の併用も可能。
| キーワード | 手法 | スキルID |
| 失敗, リスク, 負債, インシデント, pre-mortem | Pre-mortem | pre-mortem |
| 攻撃, セキュリティ, 悪用, 脆弱性, war-game | War Game | war-game |
| 論理, 判断, 根拠, なぜ, 代替案, logic | Logic Torturing | logic-torturing |
| 自己矛盾, contradiction, 宣言と実装, declared but | Self-Contradiction | self-contradiction |
| 削減, 完了, 全て置換, all replaced, -N%, リファクタ | Refactor-Claim Audit | refactor-claim-audit |
| caller, 残骸, 参照漏れ, 再採番, leakage | Cross-File Leakage | cross-file-leakage |
| 敵対的, adversarial, 全部, フル | 全手法実行 | 上記6つすべて |
デフォルト動作
- キーワード指定なし → 変更内容から自動判定:
- 設計ドキュメント/ADR → Pre-mortem + Logic Torturing
- セキュリティ関連コード → War Game + Logic Torturing
- 一般的なコード変更 → Logic Torturing
- 宣言的フレーズ(「禁止」「必ず」「MUST」等)を含む変更 → Self-Contradiction
- 完了主張(「全置換」「-N%」等)を含む commit/PR → Refactor-Claim Audit
- 構造変更(再採番・シンボル改名・分割)を含む変更 → Cross-File Leakage
- 大規模変更(ファイル数10以上or差分500行以上)→ 全手法実行
Execution Flow / 実行フロー
1. 変更内容の分類
├─ 設計/ADR → Pre-mortem を優先実行
├─ セキュリティ関連 → War Game を優先実行
├─ 判断を含む変更 → Logic Torturing を実行
├─ 宣言的フレーズ → Self-Contradiction を実行
├─ 完了主張 → Refactor-Claim Audit を実行
└─ 構造変更 → Cross-File Leakage を実行
2. 各手法の実行(並列可能)
├─ Pre-mortem: 失敗シナリオ × 最大5件
├─ War Game: 攻撃シナリオ × 最大5件
├─ Logic Torturing: 論理検証 × 最大5件
├─ Self-Contradiction: 宣言と実装の乖離 × 最大5件
├─ Refactor-Claim Audit: 完了主張の反証 × 最大5件
└─ Cross-File Leakage: caller 側残骸 × 最大5件
3. 統合サマリの生成
├─ 重複する指摘の統合
├─ 重大度による優先順位付け
└─ Human Handoff 条件の判定Output Format / 出力形式
## 🔍 Adversarial Review Summary
### 検出された盲点: N件
- Pre-mortem: X件 (失敗シナリオ)
- War Game: Y件 (攻撃シナリオ)
- Logic Torturing: Z件 (論理的な穴)
- Self-Contradiction: A件 (宣言と実装の乖離)
- Refactor-Claim Audit: B件 (完了主張の反証)
- Cross-File Leakage: C件 (caller 側残骸)
### 最も重大な発見
<最も致命的な1件の要約>
### 詳細
(各手法の出力を統合)他スキルとの関係
| 既存スキル | 関係 | 棲み分け |
architecture-risk-register | 補完 | risk-register は「リスクが文書化されているか」を確認。Pre-mortem は「文書化されていないリスクを発見」する |
security-basic | 補完 | security-basic は既知パターン(SQLi, XSS等)を検出。War Game は「既知パターンに当てはまらない攻撃経路」を発見する |
adr-decision-quality | 補完 | adr-decision は ADR の形式品質を確認。Logic Torturing は「記述された判断の論理的強度」を検証する |
References
- TECHNIQUES.md: 3手法の理論的背景と実践ガイド
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

