菜单
plcopen 提交前门禁——全量测试、RT 扫描、回放校验的准确命令与已知误报坑。Use before any commit/push in this repo, when the user says 门禁/gates, or when another skill finishes an implementation step.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
plcopen 对抗性探测轮——系统性猎杀未声明缺陷（KB-051 方法论流程化）。Use when a milestone closes, when the maintainer questions a capability claim, or when auditing semantic parity across domains.
plcopen 提交信息格式——angular 类型 + 中文四段正文 + KB/声明变更标注 + AI 声明。Use when committing in this repository.
plcopen 出处纪律——禁止来源清单与外部代码/文档引入规则。Use before referencing external implementations, vendoring third-party content, or writing planner/OTG/blending algorithms.
plcopen 新特性/新语义的规格先行全流程（语义矩阵 → 人批 → 测试先行 → 门禁 → 文档同步）。Use when adding any new capability, FB semantics, planner behavior, or when the user proposes a feature touching core/.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
plcopen harness 与文档体系的路由索引。
| name | plcopen-gates |
| description | plcopen 提交前门禁——全量测试、RT 扫描、回放校验的准确命令与已知误报坑。Use before any commit/push in this repo, when the user says 门禁/gates, or when another skill finishes an implementation step. |
按序执行，全绿才允许提交。构建目录惯例：build-sync（VS 2026）。
cmake --build build-sync --config Debug # 0 error
ctest --test-dir build-sync -C Debug --output-on-failure # 100% pass
cmake -P cmake/rt_safety_scan.cmake # RT-safety scan passed
cmake -P cmake/verify_replay_fixtures.cmake # fixtures verified
git diff --check # 只允许 CRLF warning
按需追加：
.\coverage.ps1 -BuildDir build-sync -Configuration Debug（门槛见 STATUS.md）build-legacy-cmp 目录（PLCOPEN_BUILD_LEGACY=ON）构建
plcopen_core_legacy_compare 并运行（exe 旁需 plcopen.dll）gh run list --limit 2（Windows CI + Linux CI 双绿）扫描目录：core/{adapters,rt,otg,geom,exec,kin,stream} + 任何含 RT-SAFE
标记的 core 文件。注释措辞要避开这些词形：
system ( —— 任何后跟 ( 的 system 单词（写 "equations (" 之类替代）new / delete / throw / try / catch（"new mode"→"next
mode"，"catch-up"→"recovery"）double/float 类型后名字含 dt/time/elapsed 的变量（时间一律
std::int64_t *_cycles）<chrono>/<thread>/<iostream>/<fstream> include0xC00000FD
栈溢出且无任何输出（Git Bash 报 exit 127）——测试台局部量一律
static（3 轴 rig 恰好没超线，别以此类推）。ctest ... | tail 之类的管道会让门禁看到 **tail 的退出码（0）**而漏掉
测试失败（2026-07-06 实例：两个 SEGFAULT 差点被放行）。门禁判定必须
直查 ctest 退出码：输出重定向到文件（ctest ... > log 2>&1; echo $?），
再从文件取摘要。
先判断是不是声明变更（见 plcopen-replay-baseline）；不是 → 你改坏了
周期路径，修代码而不是改基线。
完成判据：上述五条命令全绿 + （如推送）CI 双绿。