一键导入
adversarial-handoff
Adversarial Handoff Workflow guidance for Fortress Rollback. Use when High-risk reviews, post-incident hardening, escalation from code review.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Adversarial Handoff Workflow guidance for Fortress Rollback. Use when High-risk reviews, post-incident hardening, escalation from code review.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Crate Publishing guidance for Fortress Rollback. Use when Publishing to crates.io, version bumps, release checklist.
Changelog Practices guidance for Fortress Rollback. Use when Writing CHANGELOG entries, deciding what to document.
Design Decision Log Pattern guidance for Fortress Rollback. Use when Architectural decisions, design alternatives, superseding prior choices.
Repository-wide engineering policy and project context for Fortress Rollback. Use when implementing, diagnosing, reviewing, testing, documenting, or releasing changes in this repository.
GitHub Actions Best Practices guidance for Fortress Rollback. Use when Writing GitHub Actions workflows, CI debugging, actionlint, caching.
Workspace Organization guidance for Fortress Rollback. Use when Organizing workspace, splitting crates, module structure decisions.
| name | adversarial-handoff |
| description | Adversarial Handoff Workflow guidance for Fortress Rollback. Use when High-risk reviews, post-incident hardening, escalation from code review. |
Use this workflow to escalate high-risk changes from standard review into focused adversarial analysis, then feed fixes back into normal review and investigation.
Trigger when changes touch:
Action:
Trigger after root-cause fix is identified in investigation.
Action:
Periodic targeted review of a hotspot module. Non-blocking for in-flight PRs unless Critical/High risk is found.
Adversarial Handoff
Mode: Pre-Merge | Post-Incident | Planned
Scope:
- path/to/file.rs: concern
- path/to/file.rs: concern
Questions:
1. Can untrusted input break invariants here?
2. Can this path desync peers under extreme values?
3. What fails closed vs fails open?
Exit Criteria:
- Critical/High findings resolved
- Regression tests added
- Reviewer verification complete
code-review.md decides whether escalation is required.investigation.md consumes findings for post-incident pattern scans.