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.
90
86%
Does it follow best practices?
Impact
95%
2.02xAverage score across 3 eval scenarios
Passed
No known issues
End-to-end contract verification workflow
Extractor used for v1
0%
100%
Extractor used for v2
0%
100%
Verifier invoked
0%
100%
old_contracts.json present
100%
100%
new_contracts.json present
100%
100%
report.json present
100%
100%
Strengthened precondition detected
33%
100%
Weakened postcondition detected
33%
100%
Violation count correct
100%
100%
Script order correct
0%
100%
LSP violation severity classification and resolution
Scripts used for extraction
0%
37%
Verifier script used
0%
37%
Broken invariant severity
0%
100%
Strengthened precondition severity
0%
100%
Weakened postcondition severity
0%
100%
LSP rule for invariants
100%
100%
Fix for broken invariant
100%
100%
Fix for strengthened precondition
100%
100%
Fix for weakened postcondition
60%
100%
report.json present
100%
100%
CI/CD pipeline integration with exit code gating
Script uses extractor for old version
0%
100%
Script uses extractor for new version
0%
100%
Script uses verifier
0%
100%
Exit code propagation
100%
100%
Exit zero on clean
80%
70%
Exit nonzero on violations
80%
80%
Violation detail in output
100%
100%
Correct script argument interface
100%
100%
Correct workflow order
0%
100%
Script is executable shell
100%
100%
0f00a4f
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.