[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KKZM422BMRVVNET794JMMS":3,"skill-same:01M6KKZM422BMRVVNET794JMMS":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M6KKZM422BMRVVNET794JMMS","tools-spin-sync",null,"Synchronize Spin\u002FPromela models with current source code and re-verify","AI-native-Systems-Research\u002Fai-native-storage-certus","AI-native-Systems-Research","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F270755458?v=4","01M6KKQWSJX0D4X33E0KKSR4WM","AI-native Systems Research","01M6KKQWXTKR6MYVQMPKVJ5WD5",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002F.claude\u002Fskills\u002Ftools-spin-sync\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"sync","Tools","tools spin sync","code","verify","model","models","name","with","re","source","source code","2026-11-10 10:12:30",false,"---\nname: tools-spin-sync\ndescription: Synchronize Spin\u002FPromela models with current source code and re-verify\nargument-hint: \"[model-name | all]\"\n---\n\nEnsure that existing Spin\u002FPromela models in `modelling\u002Fspin\u002F` accurately reflect the current source code, then re-run model checking to confirm the properties still hold.\n\n## Input\n\nThe user provides one of:\n- A specific model name (subdirectory under `modelling\u002Fspin\u002F`, e.g. `write-before-evict`, `no-lost-extents`)\n- `all` — synchronize every model found in `modelling\u002Fspin\u002F`\n- No argument — present the list of available models and ask the user to choose one or all\n\n## Steps\n\n### Step 1: Discover models\n\nList all subdirectories under `modelling\u002Fspin\u002F` that contain a `.pml` file and a `README.md`. Each such directory is a model.\n\nIf no argument was provided, present the list and ask:\n\n> Which model(s) would you like to synchronize?\n> 1. write-before-evict\n> 2. no-lost-extents\n> 3. (other models...)\n> A. All of the above\n\n### Step 2: For each selected model, perform the synchronization\n\n#### 2a. Read the model's README.md\n\nExtract from the README:\n- The **\"Correspondence to Source Code\"** table — this maps model locations to source files and line ranges\n- The **\"Properties Verified\"** table — the invariants the model checks\n- The **\"System Abstraction\"** table — how real components map to Promela processes\n- The **\"Assumptions \u002F Stubs\"** section — what is abstracted away\n\n#### 2b. Read the current source code\n\nFor each entry in the Correspondence table, read the referenced source file and the indicated line range (plus ~50 lines of context on each side to detect if the logic has shifted).\n\n#### 2c. Read the existing .pml model\n\nRead the full Promela specification to understand the current model logic.\n\n#### 2d. Identify divergences\n\nCompare the model against the source and look for:\n\n1. **Structural changes** — The source code logic has been refactored, moved to different functions\u002Ffiles, or the control flow has changed in ways the model doesn't capture.\n2. **New states or transitions** — New code paths have been added (e.g., a new error handling branch, a new concurrent actor, a new state in an enum) that the model doesn't cover.\n3. **Removed paths** — Code paths the model exercises no longer exist in the source.\n4. **Semantic changes** — The synchronization protocol has changed (e.g., lock ordering, channel semantics, atomic sections) but the model still uses the old protocol.\n5. **Line range drift** — The code is substantively the same but has shifted to different line numbers (cosmetic — update the README only).\n\n#### 2e. Report findings\n\nFor each model, report one of:\n\n- **IN SYNC** — The model accurately reflects the current source. No changes needed. (Proceed directly to Step 3.)\n- **LINE DRIFT ONLY** — The logic is unchanged but line numbers in the Correspondence table are stale. Update the README table. (Proceed to Step 3.)\n- **MODEL UPDATE REQUIRED** — The source has diverged materially. List the specific divergences found.\n\n#### 2f. Update the model (if required)\n\nIf the model requires updating:\n\n1. **Explain the divergence** to the user: what changed in the source, and how the model must adapt.\n2. **Update the .pml file** to reflect the new source code logic. Preserve the existing model's style and conventions:\n   - Keep the same parameter names and sizes (unless the change requires new parameters)\n   - Keep the same property IDs (P1, P2, ...) where they still apply\n   - Add new properties if new invariants are now relevant\n   - Remove properties if they no longer apply (explain why)\n   - Maintain the header comment block format\n3. **Update the README.md** — refresh the Correspondence table with correct line ranges, update Properties Verified if changed, update System Abstraction if new processes were added\u002Fremoved.\n\n### Step 3: Run model checking\n\nFor each model (whether updated or unchanged):\n\n```bash\ncd modelling\u002Fspin\u002F\u003Cmodel-name>\nmake clean\nmake\n```\n\nReport the results:\n- **PASS**: errors = 0, state count, depth reached, unreached states\n- **FAIL**: assertion violation or invalid end-state found. In this case:\n  1. Run `spin -t -p \u003Cmodel>.pml` to get the error trail\n  2. Analyze the counterexample\n  3. Determine if the model is wrong (fix it) or if a real bug was found (report it to the user with the trail)\n  4. Re-run verification after fixes\n\nIf Spin is not installed (`\u002Fusr\u002Flocal\u002Fbin\u002Fspin` missing), warn the user and skip verification.\n\n### Step 4: Summary report\n\nPresent a final summary table:\n\n| Model | Status | Divergences | Verification | States | Unreached |\n|-------|--------|-------------|--------------|--------|-----------|\n| write-before-evict | IN SYNC | — | PASS | 12345 | 0 |\n| no-lost-extents | UPDATED | new abort path | PASS | 67890 | 0 |\n\n## Notes\n\n- Models are always found at `modelling\u002Fspin\u002F\u003Cname>\u002F\u003Cname_underscored>.pml` (name uses hyphens for the directory, underscores for the .pml filename).\n- The Makefile in each model directory provides the `make`\u002F`make clean` targets.\n- If a model update introduces new processes or significantly changes the state space, re-tune the parameters to keep verification tractable (\u003C10M states). Document parameter changes in the README.\n- Never delete existing properties unless the invariant is provably no longer meaningful. If unsure, keep it and note it as \"legacy — source no longer exercises this path directly.\"\n- If the source change reveals a potential real concurrency bug (model finds a valid counterexample that corresponds to reachable code), halt the sync and report the finding prominently to the user.\n","Ensure that existing Spin\u002FPromela models in `modelling\u002Fspin\u002F` accurately reflect the current source code, then re-run model checking to confirm the properties still hold.\n\n## Input\n\nThe user provides one of:\n- A specific model name (subdirectory under `modelling\u002Fspin\u002F`, e.g. `write-before-evict`, `no-lost-extents`)\n- `all` — synchronize every model found in `modelling\u002Fspin\u002F`\n- No argument — present the list of available models and ask the user to choose one or all\n\n## Steps\n\n### Step 1: Discover models\n\nList all subdirectories under `modelling\u002Fspin\u002F` that contain a `.pml` file and a `README.md`. Each such directory is a model.\n\nIf no argument was provided, present the list and ask:\n\n> Which model(s) would you like to synchronize?\n> 1. write-before-evict\n> 2. no-lost-extents\n> 3. (other models...)\n> A. All of the above\n\n### Step 2: For each selected model, perform the synchronization\n\n#### 2a. Read the model's README.md\n\nExtract from the README:\n- The **\"Correspondence to Source Code\"** table — this maps model locations to source files and line ranges\n- The **\"Properties Verified\"** table — the invariants the model checks\n- The **\"System Abstraction\"** table — how real components map to Promela processes\n- The **\"Assumptions \u002F Stubs\"** section — what is abstracted away\n\n#### 2b. Read the current source code\n\nFor each entry in the Correspondence table, read the referenced source file and the indicated line range (plus ~50 lines of context on each side to detect if the logic has shifted).\n\n#### 2c. Read the existing .pml model\n\nRead the full Promela specification to understand the current model logic.\n\n#### 2d. Identify divergences\n\nCompare the model against the source and look for:\n\n1. **Structural changes** — The source code logic has been refactored, moved to different functions\u002Ffiles, or the control flow has changed in ways the model doesn't capture.\n2. **New states or transitions** — New code paths have been added (e.g., a new error handling branch, a new concurrent actor, a new state in an enum) that the model doesn't cover.\n3. **Removed paths** — Code paths the model exercises no longer exist in the source.\n4. **Semantic changes** — The synchronization protocol has changed (e.g., lock ordering, channel semantics, atomic sections) but the model still uses the old protocol.\n5. **Line range drift** — The code is substantively the same but has shifted to different line numbers (cosmetic — update the README only).\n\n#### 2e. Report findings\n\nFor each model, report one of:\n\n- **IN SYNC** — The model accurately reflects the current source. No changes needed. (Proceed directly to Step 3.)\n- **LINE DRIFT ONLY** — The logic is unchanged but line numbers in the Correspondence table are stale. Update the README table. (Proceed to Step 3.)\n- **MODEL UPDATE REQUIRED** — The source has diverged materially. List the specific divergences found.\n\n#### 2f. Update the model (if required)\n\nIf the model requires updating:\n\n1. **Explain the divergence** to the user: what changed in the source, and how the model must adapt.\n2. **Update the .pml file** to reflect the new source code logic. Preserve the existing model's style and conventions:\n   - Keep the same parameter names and sizes (unless the change requires new parameters)\n   - Keep the same property IDs (P1, P2, ...) where they still apply\n   - Add new properties if new invariants are now relevant\n   - Remove properties if they no longer apply (explain why)\n   - Maintain the header comment block format\n3. **Update the README.md** — refresh the Correspondence table with correct line ranges, update Properties Verified if changed, update System Abstraction if new processes were added\u002Fremoved.\n\n### Step 3: Run model checking\n\nFor each model (whether updated or unchanged):\n\n```bash\ncd modelling\u002Fspin\u002F\u003Cmodel-name>\nmake clean\nmake\n```\n\nReport the results:\n- **PASS**: errors = 0, state count, depth reached, unreached states\n- **FAIL**: assertion violation or invalid end-state found. In this case:\n  1. Run `spin -t -p \u003Cmodel>.pml` to get the error trail\n  2. Analyze the counterexample\n  3. Determine if the model is wrong (fix it) or if a real bug was found (report it to the user with the trail)\n  4. Re-run verification after fixes\n\nIf Spin is not installed (`\u002Fusr\u002Flocal\u002Fbin\u002Fspin` missing), warn the user and skip verification.\n\n### Step 4: Summary report\n\nPresent a final summary table:\n\n| Model | Status | Divergences | Verification | States | Unreached |\n|-------|--------|-------------|--------------|--------|-----------|\n| write-before-evict | IN SYNC | — | PASS | 12345 | 0 |\n| no-lost-extents | UPDATED | new abort path | PASS | 67890 | 0 |\n\n## Notes\n\n- Models are always found at `modelling\u002Fspin\u002F\u003Cname>\u002F\u003Cname_underscored>.pml` (name uses hyphens for the directory, underscores for the .pml filename).\n- The Makefile in each model directory provides the `make`\u002F`make clean` targets.\n- If a model update introduces new processes or significantly changes the state space, re-tune the parameters to keep verification tractable (\u003C10M states). Document parameter changes in the README.\n- Never delete existing properties unless the invariant is provably no longer meaningful. If unsure, keep it and note it as \"legacy — source no longer exercises this path directly.\"\n- If the source change reveals a potential real concurrency bug (model finds a valid counterexample that corresponds to reachable code), halt the sync and report the finding prominently to the user.\n",{"name":5,"description":7,"argument-hint":36},"[model-name | all]","unstable","dc564aa356769b7754391c9fa4fdaa0f179f476c",".claude\u002Fskills\u002Ftools-spin-sync",4,"https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research","https:\u002F\u002Fai-native-systems-research.github.io\u002Fai-native-systems-research\u002F","2026-11-12 06:08:32",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill tools-spin-sync",{"tool":51,"command":52},"bunx","bunx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill tools-spin-sync",{"tool":54,"command":55},"pnpm","pnpm dlx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill tools-spin-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002F.claude\u002Fskills\u002Ftools-spin-sync\u002FSKILL.md",true,[],[60,65,81,92,109,121],{"skillNo":61,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":31},"01M6KP29TWSNGADF3AJ47BR7TY","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-spin-sync\u002FSKILL.md",[],[21,20,19,22,23,24,25,26,27,28,29,30],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":31},"01M6KP277TDY3ZAJEBP5P6MDT8","tools-spin-model","Create a new Spin\u002FPromela formal verification model for a system property","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-spin-model\u002FSKILL.md",[],[72,24,20,73,74,75,76,77,78,79,80],"tools spin model","system","formal verification","number","for","prove","new","create","verification",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":31},"01M6KP250W406CEDSF02BRXT9D","tools-creusot-install","Install the Creusot Rust verification tool","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-install\u002FSKILL.md",[],[88,89,20,90,80,91],"tools creusot install","install","rust","tool",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":31},"01M6KP22H28FQ1X0V7VJHEFWXD","tools-creusot-init","Prepare an existing Cargo project to use Creusot formal verification","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-init\u002FSKILL.md",[],[99,20,100,101,102,103,104,80,105,74,106,107,108],"tools creusot init","init","project","directory","components","prepare","use","cargo","manager","Existing",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":31},"01M6KP1V506J9YM8DKKVDG1NRE","tools-creusot-coq-install","Add Coq 8.20 as an additional prover to an existing Creusot installation, for verification conditions that SMT solvers cannot discharge","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-coq-install\u002FSKILL.md",[],[116,117,89,20,76,108,118,119,80,120],"tools creusot coq install","Coq","as","installation","add",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":31},"01M6KP1PQJF3H765TYZAZ7P3EF","tools-creusot-annotate-interfaces","Formally verify a component's properties with Creusot and annotate its interface definitions","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-annotate-interfaces\u002FSKILL.md",[],[20,128,129,27,26,130,23,131,132],"tools creusot annotate interfaces","annotate","properties","component","interface"]