acceptance-gates
Skill0 starsChanged 5 months agoApache-2.0View on GitHub
GEODoctor 各类变更的完成定义(DoD)——不确定"做到什么程度才算完"时使用。新规则、bug 修复、文档、发版四类门禁+覆盖率真相。
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- architecture-contractsSkill
- bilingual-docs-contractSkill
- debug-audit-pipelineSkill
- debug-site-quirksSkill
- debug-test-failuresSkill
- diagnostic-commandsSkill
- evidence-registry-contractSkill
- failure-archaeologySkill
- release-versioning-controlSkill
- rule-change-controlSkill
- security-boundariesSkill
- showcase-refresh-protocolSkill
- skill-mapSkill
The file
Files
验收门禁(Definition of Done)
适用场景
自查或评审:这个改动可以合入了吗?
门禁 A:新增/修改规则
- 证据先行:evidence id 已按 evidence-registry-contract 入册(这是硬门,无证据的规则直接拒——CONTRIBUTING 对外也这么承诺的)
tests/version.test.ts的规则总数断言已同步(当前 33)- 正反测试齐:pass 路径 + fail 路径 +(若有适用门槛)na 路径
- 双语文案过 bilingual-docs-contract 三条红线
- 站点来源字符串进 finding 前已过
stripControlChars(security-boundaries D2) docs/methodology.md手工规则表已同步(没有自动同步,全靠这条清单)- 若影响打分:showcase 榜单已按 showcase-refresh-protocol 重跑
pnpm typecheck && pnpm test且退出码亲眼确认(管道吞码事故后的铁律,见 failure-archaeology 案 1)pnpm test:coverage本地过门槛(绿 CI ≠ 覆盖率达标,见下方"覆盖率真相")
门禁 B:bug 修复
- 先有失败测试复现,后有修复让它变绿——顺序不能反(本仓库 TDD 规矩的最低执行线)
- 若 bug 属于"站点敌对输入"类:回归测试写进
tests/security.test.ts并对照 security-boundaries 三道防线归位 - 值得后人记住的坑 → 按模板归档进 failure-archaeology
门禁 C:文档
- 快速开始/安装区块的命令当下可跑——npm 未发布期间该区块不许出现
npx geo-doctor;用法示例段允许按发布后形态书写、"即将发布"预告句除外(此刻的临时状态;发布后按 release-versioning-control 改回)。检验法:把快速开始命令粘进新终端跑一遍 - 中英镜像文件同步检查(bilingual-docs-contract 的镜像清单)
- 徽章不许 404(npm 徽章在包发布前不挂)
门禁 D:发版
全套见 release-versioning-control;本门只留一句:版本号双源(package.json + src/version.ts)+ stub 承诺(v0.2 必须先有 probe/fix 之一)。
覆盖率真相(自查时别被骗)
- CI 跑的是
pnpm test,不含 coverage——绿 CI ≠ 覆盖率达标 - 本地
pnpm test:coverage的门槛:lines/functions/statements 80%、branches 70% fetcher.ts与site.ts的网络 IO 主路径不写单测是显式共识(实测语句覆盖 5%/17%,由真实站点冒烟兜底):不要为网络路径凑 mock 单测,也不要引用这两个文件的低覆盖给自己的新代码免测——豁免仅限网络 IO 路径。其中的纯函数不在豁免内(先例:site.ts 的safePublicUrl有直接单测)- 冒烟标准:
node dist/cli.js audit <真实站点>三种输出(终端/HTML/JSON)各验一次
什么时候不该用这份文档
- 想知道怎么做改动 → 各 control/debug 文档;本门只管何时算完
- 架构级不变量是否被破坏 → architecture-contracts(那是设计约束,不是完成度清单)
- 社区发布(发帖)的检查清单 →
LAUNCH.local.md
姊妹文档
rule-change-control(门禁 A 的过程版)· release-versioning-control(门禁 D 全文)· failure-archaeology(门禁 B 的归档出口)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

