Menu

Individual skill

maintain-formal-verification-skill

Re-sync formal checks whose code moved on since they last ran, rerun them, and decide for each failure whether the check went stale or the code broke. Triggers: /maintain-formal-verification-skill, asking whether a model still matches its code, or merges and refactors in verified areas.

plugins/requie/endostack/skills/maintain-formal-verification-skill/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# maintain-formal-verification-skill

A model left behind by a code change can go on passing even though it describes code that is gone. Nobody questions such a pass, since it reads exactly like a real proof, and that makes it more dangerous than an outright failure. Here you locate the commits that changed verified code, rewrite the model, harness or property so it matches the current code, run the check again, and judge each failure as either an out-of-date verification or a genuine defect.

The generated verify skill covers edits an agent makes while following it. This skill covers everything that went around it: merged branches, hand edits, and drift across many commits.

If the repo has no formal verify skill, point the user to the `create-formal-verification-skill` skill ([../create-formal-verification-skill/SKILL.md](../create-formal-verification-skill/SKILL.md)).

## Verdicts

Give every check one verdict, or two where noted:

- **in sync**: nothing since the sync commit changes what the check models, and it passes.
- **updated**: code changed, the verification was revised to match, and it passes.