correctness-gate

仓库创建 2026年7月6日最近提交 21 天前SkillHot 收录 20 天前

▸ 精选理由

适合含核心计算模块的项目，保证改动不会隐性破坏结果。

这个 Skill 做什么

在关键模块修改后强制运行门控测试以确保不破坏结果。

在触及关键模块后强制跑门控测试，只有门通过才能把改动标记为“完成”。用于任何可能悄悄改变结果的核心模块改动，或门测失败时要判断是 bug 还是刻意改动。这个机制把“看不见的数值变化”当作报警线，防止静默破坏科研或业务结果。

▸ 展开 SKILL.md 英文原文

Use when a change touches any critical module — the modules whose silent breakage would corrupt the project's results — before claiming the change is done, ready, or working. Also use when the named gate test goes red and the bug-or-intentional-change call must be made. Trigger phrases: "run the gate", "is the correctness gate green", "I changed the core model", "the gate is red", "can I say this is done", "update the gate tolerance".

研究检索关键模块门控测试防回归通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/huguryildiz/ALETHEIA/main/skills/core/correctness-gate/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/huguryildiz/ALETHEIA/main/skills/core/correctness-gate/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# correctness-gate

The project names a set of critical modules (`{{critical_modules}}`) and one gate command
(`{{gate_command}}`). The contract: **if any critical module changed, "done" may not be said
until the gate passes.** Silent breakage in these modules does not crash — it quietly
changes numbers, and wrong numbers end up in the paper. The gate is the tripwire.

## When to use

- Any edit lands inside `{{critical_modules}}` — run the gate before reporting completion.
- The gate is red and you must decide: bug, or intentional formulation change?
- A new module is becoming result-critical and should enter the gate's scope.

## When NOT to use

- Changes outside `{{critical_modules}}` (o

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有