check-regressions

Detect Dafny specification changes requiring re-verification via git diffs and source hashes.

5|Updated Mar 4, 2026

Search Tags:#verification #regression #formal methods #code verification #dafny

Ready to run

npx skills add https://github.com/nicholls-inc/claude-code-marketplace --skill check-regressions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-regressions
Source: https://github.com/nicholls-inc/claude-code-marketplace/tree/main/crosscheck/skills/check-regressions
Command: npx skills add https://github.com/nicholls-inc/claude-code-marketplace --skill check-regressions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill detects when code modifications cause previously verified Dafny specifications to become invalid, helping maintain verified code quality over time.

Core Features & Use Cases

Regression Detection: Identifies changed code or specifications that require re-verification.
Change Summary: Provides a clear overview of which specs have been altered or deleted.
Use Case: Developers can quickly verify if recent code changes compromise existing formal guarantees, facilitating continuous correctness assurance.

Quick Start

Run the check-regressions skill to scan all registered specifications and identify any that need re-verification.

Frequently Asked Questions about check-regressions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect verification regressions in Dafny specifications after code changes?▼

To detect verification regressions in Dafny specifications, scan all registered files to identify changed code or specifications that require re-verification. This validates code consistency and tracks changes via git diffs and source hashes.

What is formal code verification regression detection?▼

Formal code verification regression detection identifies when software modifications cause previously verified Dafny specifications to become invalid, preventing silent regressions in formally verified systems and ensuring ongoing verification integrity.

How do I check if recent changes break existing formal verification guarantees?▼

To check if recent changes break existing formal verification guarantees, run a scan of all registered Dafny specifications. This provides a clear summary of which specs have been altered or deleted and require re-verification.

Can I use git diffs to track Dafny specification changes for continuous correctness?▼

Yes, you can use git diffs to track Dafny specification changes for continuous correctness. The process validates code consistency with Dafny verification results by tracking source file changes through git diffs and source hashes.

When do I need to re-verify formally verified code?▼

You need to re-verify formally verified code whenever modifications cause previously verified Dafny specifications to become invalid. Detecting these regressions ensures that recent code changes do not compromise existing formal guarantees.