Formal Verify Delivery Cycle
有界穷举检查 delivery-cycle 维护入口的时序与重试性质(R8 不写回旧周、R9 先读后写不盲重放、verified 必有回读、partial 不冒充 synchronized、R11 重跑零写入)。改动 skills/delivery-cycle/scripts/delivery-cycle.js 的执行、前读、写入、回读、时钟或结果判定代码,或改 tests/fake-adapters.js 时使用。
Install
npx skills add Dimon94/skills --skill formal-verify-delivery-cyclegit clone --depth 1 https://github.com/Dimon94/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/formal-verify-delivery-cycle ~/.claude/skills/formal-verify-delivery-cyclePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# formal-verify-delivery-cycle 在每个 port `await` 前穷举注入原生滚动、他人手动移动、跨周一与写读故障,跑真实 `maintainCurrentWeek`,检查五条性质。这是有界调度探索,不是无界证明,也不代替真实 Linear 验收。 ## 1. 判断改动是否命中 ```bash git diff --stat 44158e12ec662cef8f29991c76630ea610616f62 -- skills/delivery-cycle/scripts/delivery-cycle.js skills/delivery-cycle/tests/fake-adapters.js ``` 有输出即命中。覆盖的函数与性质见 [references/coverage.md](references/coverage.md)。只改 `assessFormalDelivery`、身份分组或 Adapter(`linear-graphql.js`、`evidence.js`、`run.js`)不命中,跑普通测试即可。 ## 2. 运行 前置:Node.js 22(已核实 v22.22.0)。无其他依赖,可离线运行。 ```bash node skills/formal-verify-delivery-cycle/scripts/verify.js ``` 约 35 秒。退出码 0 且末行 `RESULT: PASS` 才算通过。可只跑一个场景:追加 `carry` 或 `exclude`。未知场景退出码 2,不执行探索,不输出 PASS。 改了覆盖代码的判断分支后,再证明检查仍能失败(约 5 分钟,会就地写入并还原 `delivery-cycle.js`,要求该文件无未提交改动): ```bash node skills/formal-verify-delivery-cycle/scripts/mutants.js ``` 末行 `MUTANTS: ALL CAUGHT` 且 `identical=true`。`MISSED` 或锚点不存在表示 `mutants.js` 跟不上代码,按第 4 节更新。退出码 2 表示还原失败:先 `git diff -- skills/delivery-cycle/scripts/delivery-cycle.js` 核对,再用 `git checkout -- skills/delivery-cycle/scripts/delivery-cycle.js` 恢复。 ## 3. 读结果 `VIOLATION <性质> run<n> <Issue>: <原因>` 之后是一条按代码名词讲的轨迹:`readIssue`、`patchIssue`、环境事件和每轮 `maintainCurrentWeek` 结果。`choices=[...]` 是该轨迹的选择序列。 先判断是代码缺陷还是建模错误: 1. 轨迹里的环境事件发生在前读之前,代码在发送时已经能看到它 → 代码缺陷。报告轨迹,不改性质、不改 `world.js` 迁就实现。 2. 环境事件只发生在 `patchIssue` 发送之后,或依赖平台不会产生的状态 → 建模错误,修 `scripts/world.js` 的注入点。 3. `unobservedRaceTraces` 非零不是失败:它数的是前读之后才发生的他人写入被本次写覆盖的轨迹。没有 CAS,Spec R8 只承诺“已观察到的不回移”。
Details
- Skill name
formal-verify-delivery-cycle- Repository
- Dimon94/skills
- Path
skills/formal-verify-delivery-cycle/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Formal Verify Delivery Cycle skill do?
有界穷举检查 delivery-cycle 维护入口的时序与重试性质(R8 不写回旧周、R9 先读后写不盲重放、verified 必有回读、partial 不冒充 synchronized、R11 重跑零写入)。改动 skills/delivery-cycle/scripts/delivery-cycle.js 的执行、前读、写入、回读、时钟或结果判定代码,或改 tests/fake-adapters.js 时使用。
How do I install the Formal Verify Delivery Cycle skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dimon94/skills --skill formal-verify-delivery-cycle. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Formal Verify Delivery Cycle popular?
It lives in Dimon94/skills, which has 107 GitHub stars and 21 forks.
Related skills
Maintain Verification Skill
107Dimon94/skills
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
Create Verification Skill
107Dimon94/skills
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
How
107Dimon94/skills
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
Godot
46Randroids-Dojo/Godot-Claude-Skills
Develop, test, build, and deploy Godot 4.x games. Includes GdUnit4 for GDScript unit tests and PlayGodot for game automation and E2E testing. Supports web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Diagnose
43aws-samples/sample-kiro-cli-multiagent-development
Investigate and fix open issues in the .kiro/issues/ folder using test-first debugging. Use when asked to diagnose, triage, or work through unresolved bug reports, or when the user mentions open issues that need fixing.
Implement
107Dimon94/skills
按 spec、计划或 tickets 实现:逐条拆验收与失败方式,按需 TDD,跑相关 E2E 与形式验证,对账后双轴审查(最多三轮),P2 登记 issue,再提交。
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.