Skip to content
cccskills
FreePublished on GitHub

interface-contract-verifier

Verify that interface and class contracts (preconditions, postconditions, invariants) are preserved across program versions. Use when validating refactorings, checking API compatibility, verifying design-by-contract implementations, or ensuring behavioral contracts remain intact after code changes. Automatically detects contract violations, identifies affected methods and classes, and provides actionable guidance for resolving violations while maintaining program correctness.

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md2.6 KB
  • references/design_by_contract.md2.1 KB
  • scripts/contract_extractor.py5.2 KB
  • scripts/contract_verifier.py9.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Interface Contract Verifier

Overview

Verify that formal or structured contracts (preconditions, postconditions, invariants) defined in interfaces and classes are preserved when updating to a new program version.

Core Workflow

1. Extract Contracts

Extract contracts from both versions:

python scripts/contract_extractor.py --program old_version --output old_contracts.json
python scripts/contract_extractor.py --program new_version --output new_contracts.json

2. Verify Contracts

Compare and verify contract preservation:

python scripts/contract_verifier.py --old old_contracts.json --new new_contracts.json --output report.json

3. Review Violations

Examine violations: weakened preconditions, strengthened postconditions, broken invariants.

Contract Types

Preconditions

Requirements before method execution:

def withdraw(amount):
    """Precondition: amount > 0 and amount <= balance"""

Postconditions

Guarantees after method execution:

def deposit(amount):
    """Postcondition: balance == old(balance) + amount"""

Invariants

Properties always true for a class:

class BankAccount:
    """Invariant: balance >= 0"""

Verification Rules

Liskov Substitution Principle:

  • Preconditions can be weakened (accept more)
  • Postconditions can be strengthened (guarantee more)
  • Invariants must be maintained

Violation Types

Strengthened Precondition (Error)

New version rejects previously valid inputs.

Weakened Postcondition (Error)

New version guarantees less.

Broken Invariant (Critical)

Class invariant no longer holds.

Resolution Guidance

Fix Strengthened Precondition

Relax precondition or update callers.

Fix Weakened Postcondition

Strengthen implementation to meet original guarantee.

Fix Broken Invariant

Add checks to maintain invariant in all methods.

Resources

  • references/design_by_contract.md: Design by Contract principles
  • scripts/contract_extractor.py: Extract contracts from code
  • scripts/contract_verifier.py: Verify contract preservation

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Applies abstract interpretation using different abstract domains (intervals, octagons, polyhedra, sign, congruence) to statically analyze program variables and infer invariants, value ranges, and relationships. Use when analyzing program properties, inferring loop invariants, detecting potential errors, or understanding variable relationships through static analysis.

The English summary is being prepared. Showing the original description.

ArabelaTso/Skills-4-SE256Updated Aug 21, 2026

Uses abstract interpretation to automatically infer loop invariants, function preconditions, and postconditions for formal verification. Generates invariants that capture program behavior and support correctness proofs in Dafny, Isabelle, Coq, and other verification systems. Use when adding formal specifications to code, generating verification conditions, inferring contracts for functions, or discovering loop invariants for proofs.

The English summary is being prepared. Showing the original description.

ArabelaTso/Skills-4-SE256Updated Aug 21, 2026

Performs abstract interpretation over source code to infer possible program states, variable ranges, and data properties without executing the program. Reports potential runtime errors including out-of-bounds accesses, null dereferences, type inconsistencies, division by zero, and integer overflows. Use when analyzing code for potential runtime errors, performing static analysis, checking safety properties, or verifying program behavior without execution.

The English summary is being prepared. Showing the original description.

ArabelaTso/Skills-4-SE256Updated Aug 21, 2026

Performs abstract interpretation to produce summarized execution traces and high-level program behavior representations. Highlights key control flow paths, variable relationships, loop invariants, function summaries, and potential runtime states using abstract domains (intervals, signs, nullness, etc.). Use when analyzing program behavior, understanding execution paths, computing loop invariants, tracking variable ranges, detecting potential runtime errors, or generating program summaries without concrete execution.

The English summary is being prepared. Showing the original description.

ArabelaTso/Skills-4-SE256Updated Aug 21, 2026

Create ACSL (ANSI/ISO C Specification Language) formal annotations for C/C++ programs. Use this skill when working with formal verification, adding function contracts (requires/ensures), loop invariants, assertions, memory safety annotations, or any ACSL specifications. Supports Frama-C verification and generates comprehensive formal specifications for C/C++ code.

The English summary is being prepared. Showing the original description.

ArabelaTso/Skills-4-SE256Updated Aug 21, 2026

CLI-based browser automation with persistent page state using ref-based element interaction. Use when users ask to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

The English summary is being prepared. Showing the original description.

ArabelaTso/Skills-4-SE256Updated Aug 21, 2026

See all skills by ArabelaTso

Report a problem with this skill