Individual skill
adversarial-review
开发完成后的三方对抗式代码评审闭环:蓝军(敌意审查,须给证据链)→ 第三方(独立审计,不信双方文档、只读代码,专找"修改引入的新缺陷"并稽核蓝军漏审的维度)→ 中立裁定(逐条采纳/驳回、审查双方共同前提)。当用户说"蓝军评审""第三方复核""对抗性审查""红蓝互搏""三方评审""交叉验证""发布前审查""帮我挑刺""adversarial review""red team review""pre-release review""critique this""find bugs in my code"或要求提升代码质量、准备发布前把关时使用。也适用于用户想把当前会话变成"多个 Agent 互搏"来提升代码水平的场景。
builtin-skills/skills/adversarial-review/SKILL.md
Source commit 32f4c02677151dc23f6d1cfe1616b04ed8918b26
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 5,375
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- openclaw Repository topic
- openclaw-skills Repository topic
- skill Repository topic
- iflytek-astron Repository topic
- skill-hub Repository topic
- skill-manager Repository topic
- skills Repository topic
- agent-framework Repository topic
- ai-orchestration Repository topic
- audit-log Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
LICENSE.txtdoc · 1,078 bytesNOTICE.mddoc · 1,131 bytesSKILL.mdcore · 14,230 bytesSKILL.mdcore · 14,230 bytesexamples/sample-review-v2.2.mddoc · 4,669 bytesexamples/sample-review.mddoc · 7,745 bytesreferences/prompt-templates.mddoc · 15,706 bytesreferences/quickstart.mddoc · 4,212 bytesreferences/review-dimensions.mddoc · 5,773 bytesscripts/check-report.mjsruns · 17,405 bytes
Read excerpt
# 三方对抗式代码评审(Blue Team / Third Party / Adjudication)
## 这个 skill 要解决什么
单人或单 AI 写代码,最大的风险不是"不会写",而是:
1. **用未验证的乐观假设说服自己推迟修复**("这个兜底应该够了吧");
2. **测试提供假安全感**(测试全绿,但功能其实早坏了);
3. **为了修 A 而引入 B**(新写的修复代码本身没被独立审视)。
这三个问题**靠"再仔细看一遍"解决不了**——写代码的人和审代码的人是同一个,就一定会为自己辩护。只能靠**结构化的对抗关系**:
| 角色 | 立场 | 硬性约束 |
|---|---|---|