364 个 · 按相关度排序
Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
中文简介正在准备中。当前显示原文说明。
Adversarial critique — devil's advocate, stress-test, honest teardown ('poke holes', 'be brutal', 'was hältst du davon'); explicit request only. Routine code or design review → code-review.
中文简介正在准备中。当前显示原文说明。
Use when reviewing PRs/diffs/branches/documents for .NET quality, correctness, performance, security, data access, messaging, and observability. Includes adversarial critical-thinking mode for skeptical/cynical review requests. Keywords: code review, review PR, review diff, critical review, cynical review, adversarial review, production readiness, low GC, AOT, security review.
中文简介正在准备中。当前显示原文说明。
Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships. Use when output must clear two independent adversarial reviewers before it ships.
中文简介正在准备中。当前显示原文说明。
Adversarial code review that breaks the self-review monoculture.
中文简介正在准备中。当前显示原文说明。
敵対的分析手法を統合したレビューの entry skill。認知バイアス対策の3手法 （Pre-mortem / War Game / Logic Torturing）と、宣言・主張と実態の乖離を突く claim-vs-actual 検出3パターン（Self-Contradiction / Refactor-Claim Audit / Cross-File Leakage）へルーティングし、通常のレビューでは見えない設計の盲点・ 防御の穴・論理の弱点・宣言と実装のズレを可視化する。
中文简介正在准备中。当前显示原文说明。
Structured methodology for adversarial thinking — generating attack scenarios, abuse cases, race conditions, and security edge cases against specs and implementations. Produces spec-level gap items, not code-level fixes.
中文简介正在准备中。当前显示原文说明。
Hostile self-review of recently written AI workflow code that then applies fixes (agents, tools, chat context, summarization, tokens, attachments). Use after generating AI systems code, or when asked to self-review and harden it. Not for PR peer review (code-review) or no-edit devil's-advocate attacks (adversarial-challenge). Prefer: adversarial-challenge → decide → this skill.
中文简介正在准备中。当前显示原文说明。
Structured 3-phase peer review of a diff or PR — intent, issues by severity, then pointed merge-readiness questions and a verdict. Use for general code review. Not for AI workflow self-fix-and-edit (ai-systems-review) or no-edit devil's-advocate threat models (adversarial-challenge). Phase 3 asks questions only; it is not the adversarial-challenge skill.
中文简介正在准备中。当前显示原文说明。
Multi-Agent Adversarial Analysis System for code security
中文简介正在准备中。当前显示原文说明。
Library of realistic adversarial attack vectors and anti-patterns to avoid. Contains examples of valid attacks and subtle gaming patterns to reject.
中文简介正在准备中。当前显示原文说明。
Fresh adversarial code review with binary PASS/FAIL verdicts, evidence citations, and anchoring bias prevention via fresh reviewer spawning.
中文简介正在准备中。当前显示原文说明。
MAGI System v2 — AoT 分解 + MELCHIOR/BALTHASAR/CASPAR 合議 + lam-harness:gabriel adversarial probe による 構造化意思決定フレームワーク。判断ポイント 2+ / 影響レイヤー 3+ / 選択肢 3+ で使用。 Use when facing complex decisions with multiple trade-offs or architectural choices.
中文简介正在准备中。当前显示原文说明。
MAGI System v2 — AoT 分解 + MELCHIOR/BALTHASAR/CASPAR 合議 + gabriel adversarial probe による 構造化意思決定フレームワーク。判断ポイント 2+ / 影響レイヤー 3+ / 選択肢 3+ で使用。 Use when facing complex decisions with multiple trade-offs or architectural choices.
中文简介正在准备中。当前显示原文说明。
Adversarial reviewer for The Federated Harbor whitepaper — the third paper in the Curiositech sequence after Anchor and Bonded Commons. Probes federation-specific threats: trust transitivity, cross-harbor token forgery, federated revocation under partition, cross-harbor Sybil, cross-domain settlement, equivocation, bond-pool draining, cold-start joining, federation-operator Sybil. Use during a versioned red-vs-white round; pairs with federated-harbor-whitehat. NOT for incident response, NOT for the Anchor or Bonded papers (use redteam-review).
中文简介正在准备中。当前显示原文说明。
codex exec review を基本に、必要なら codex exec を使ってコード変更のレビューを依頼し、指摘事項を報告する。通常 / 厳しめ (--strict) / 敵対的 (--adversarial、実装を壊しにいく red team) の 3 モードを持つ。「codexでレビューして」「codex-review」「/codex-review」「敵対的にレビューして」で発火。Codex 単体での単独レビュー用途。複数エージェント並行レビューは cross-review、差分ではなくコードベース全体の監査は audit を使う。
中文简介正在准备中。当前显示原文说明。
Roleplay the most difficult, tech-resistant user for your product. Browse the app as that persona, find every UX pain point, then filter complaints through a pragmatism layer to separate real problems from noise. Creates actionable tickets from genuine issues only.
中文简介正在准备中。当前显示原文说明。
在发布文章或部署代码前，由两个独立代理按相同标准审查；仅在双方均通过后继续，否则修改并重新审查，达到迭代上限后将未解决的问题交由人工判断。
将大型功能开发或迁移目标拆成可分多次执行的计划，整理每个步骤的背景、依赖关系和验证方法，支持将工作交接给其他代理。
在实施前通过有针对性的追问，明确计划的目标、约束、技术选择和异常应对。按决策依赖关系逐轮提问，整理已定事项与未解决问题，统一理解。
扮演不擅长技术、容易不满的用户测试应用，发现难懂的操作和导致放弃使用的障碍。将实际可改进的问题与个人抱怨分开，整理截图、修复建议和任务单。
将大批文件修改或调查分配给多个智能体，核验后整合结果。把计划和中间成果保存在文件中，通过反证检查结论，并分阶段推进任务。
将设计或实现中的重要决策交给不继承工作过程的独立审查者验证，找出隐藏前提和失败条件，再据此修正问题或重新评估决策。
面向开发与研究，指导使用RuView整合多个WiFi观测点的信号，研究位置估计、三维空间占用重建、长期运动趋势变化，以及针对可疑信号的防御。