Integration Contract Auditor

Use this skill to review schema quality and detect payload drift before an integration goes live.

Workflow

1. Provide an expected schema or payload and optionally an actual runtime payload.

2. Run scripts/audit_contracts.py.

3. Fix block findings before release; warnings should become test cases.

Usage

python3 scripts/audit_contracts.py --expected expected.json --actual actual.json
python3 scripts/audit_contracts.py --schema-text '{"type":"object","properties":{"id":{"type":"string"}}}'
python3 scripts/audit_contracts.py --self-test

Parameters

• --expected: Expected JSON schema or representative payload file.
• --actual: Actual JSON payload file to compare against expected.
• --schema-text: Inline JSON schema/payload text.
• --json: Emit JSON.

Guardrails

• Do not pass raw secrets or full production payloads containing PII.
• Redact token/password/secret fields or require a data-handling control.
• Treat required-field/type drift as release-blocking.

Local Verification

python3 scripts/audit_contracts.py --self-test

Use --self-test before handing off; Viper should see weak contracts warn, type drift block, and sensitive fields require redaction controls.