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

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• reverse-engineer-anything 456,474 ★
  Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and b
• mattpocock-skills 323,337 ★
  Matt Pocock's agent skills for real engineering — grilling, spec/ticket flows, TDD, code review, domain modell
• scaffold-exercises 323,337 ★
  Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use
• wait-what 323,337 ★
  Stop. That last message did not land: re-pitch it.
• template-skill 194,218 ★
  Replace with description of the skill and when Claude should use it.