Maintain Formal Verification Skill
Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, "is the model still true to the code", or after merges and refactors that touched verified code without rechecking it.
Install
npx skills add Dimon94/skills --skill maintain-formal-verification-skillgit clone --depth 1 https://github.com/Dimon94/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/maintain-formal-verification-skill ~/.claude/skills/maintain-formal-verification-skillPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Maintain a formal verification skill A formal check proves a property of what it describes. When the code changes and the verification does not, the check can keep passing while it describes code that no longer exists. That pass is the dangerous case, because it looks like a proof. This skill is the upkeep loop for a verify skill that `/create-formal-verification-skill` generated, or for any project-local skill that runs a model checker, prover, or code-level verifier against named code. The project-local skill handles a change that an agent makes while it uses that skill. This skill handles the changes that skipped it: merges, edits made without the skill, and drift that builds up across many commits. ## Outcomes Give each check one outcome, and say which: - **in sync**: no change since the last sync alters what the check describes, and the check passes. - **updated**: the code changed, the verification now describes the new code, and the check passes. - **bug**: the verification describes the current code, and the code breaks the property. This is a finding about the code. It is not drift. - **blocked**: the check could not be brought back in line or could not run. Say exactly why. A check can be both updated and bug: the update makes the verification describe the code again, and then the property fails on it. ## Edit scope
Details
- Skill name
maintain-formal-verification-skill- Repository
- Dimon94/skills
- Path
skills/maintain-formal-verification-skill/SKILL.md- Repo updated
- 18 November 2026
- Copies
- Found in 2 GitHub repos
FAQ
What does the Maintain Formal Verification Skill skill do?
Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, "is the model still true to the code", or after merges and refactors that touched verified code without rechecking it.
How do I install the Maintain Formal Verification Skill skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dimon94/skills --skill maintain-formal-verification-skill. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Maintain Formal Verification Skill 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.
Building Browser Extensions
115wdm0006/python-skills
Builds and tests Manifest V3 browser extensions — service-worker message channels that survive teardown, chrome.storage read-modify-write safety, settings validation in the popup, and a Jest chrome mock that can actually fail. Use when writing or reviewing a background service worker, a popup that reads/writes chrome.storage, an extension's Jest suite, or debugging an extension whose UI silently stops responding.
Simplify
75sneg55/agent-starter
Review changed code for reuse, quality, and efficiency, then fix any issues found.
Building Go Projects
115wdm0006/python-skills
Sets up and maintains Go projects with a CI gate that actually gates — module-path correctness, golangci-lint config that matches the installed major version, deterministic gofmt, a pinned toolchain, and meaningful test/lint jobs. Use when creating a Go module, wiring GitHub Actions for Go, debugging a golangci-lint or gofmt CI failure on an unrelated PR, or reviewing a Go CLI that shells out to git/gh.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.