adversarial-validation
GitHub针对RustFS的高风险变更执行对抗性代码审查，依据风险等级选择正确性、安全等维度探针进行验证，确保变更符合仓库规范。
Trigger Scenarios
Install
npx skills add rustfs/rustfs --skill adversarial-validation -g -y
SKILL.md
Frontmatter
{
"name": "adversarial-validation",
"description": "Review RustFS diffs or designs for explicit adversarial requests, high-risk changes under the repository review policy, or substantial PR reviews. Skip ordinary questions, diagnosis, planning, status, routine low-risk implementation, and prose with no execution effect."
}
RustFS Adversarial Validation
Use the repository risk tiers and review shape. This skill routes a review to RustFS-specific probes without loading unrelated domains.
Select Lenses
Read only the references required by the diff:
| Lens | When to read |
|---|---|
| Correctness | Every non-exempt adversarial review |
| Simplicity | Mechanical/standard changes and production growth |
| Test coverage | Behavior or test changes |
| Security | Authn/authz, IAM, RPC trust, paths, secrets, parsing, browser, encryption |
| Concurrency/durability | Async shared state, locks, storage commit, cancellation, persisted queues |
| Compatibility | S3 surface, MinIO interop, metadata, wire/disk formats, mixed versions |
| Performance | Request/object hot paths, allocation, blocking work, fsync, fan-out |
Do not read all references as a precaution. A path name alone is insufficient; the changed behavior must touch the lens's domain.
For a dedicated security audit or advisory analysis, use
security-advisory-lessons instead of loading it automatically during every
adversarial review.
Review Protocol
- Freeze the exact final diff/head (or the design under review) and list the selected lenses.
- Run the review shape required by the repository risk tier.
- For each selected lens, either report a concrete finding or a null verdict naming the attacks performed.
- Apply root
AGENTS.md's finding standard. Test each candidate against callers, existing coverage, and invariants before accepting it; an adversarial role does not have to produce a defect. - Fix or rebut supported findings with code-path, test, or invariant evidence.
- After a non-trivial edit, rerun only lenses affected by that edit against the new exact diff.
Do not turn a null verdict into a long checklist. Record concise evidence that the relevant failure classes were attacked, then stop under the root completion rule. Keep the required per-lens verdicts for high-risk PRs.
Version History
-
1880b42
Current 2026-09-23 05:25
将review shape来源从根AGENTS.md统一引用至references/adversarial-validation.md；细化Review Protocol步骤3的描述以明确null verdict的攻击测试要求。
-
0fe41da
2026-08-29 02:10
重构审查流程，从角色剧本改为基于差异触发的透镜选择机制，优化引用加载策略。
- 0d129ec 2026-08-20 14:32
