contract-check

Contract Check — Pact Health Auditor

Audits the health of consumer-driven contract tests across all letterbox services. Surfaces staleness, sync gaps, uncommitted pacts, missing tests, documentation drift, and disabled tests.

This is a read-only audit — it does not run tests or modify files. Use /contract-test to execute contract test workflows.

When to Use

• Starting a work session to check contract health
• After modifying connectors or API endpoints
• Before a release to verify all contracts are synced and committed
• Periodically to catch drift and gaps

Usage

/contract-check              # Full audit (all checks)
/contract-check status       # Summary dashboard only
/contract-check stale        # Consumer output newer than provider copy
/contract-check uncommitted  # Pact files not committed in service repos
/contract-check sync-gaps    # Trace each intended edge: consumer test → built pact → synced to provider
/contract-check coverage     # Provider CI verifies each synced pact? (catches commented-out/disabled consumers)
/contract-check missing      # Connectors with no consumer tests
/contract-check docs         # Documentation drift in pact-workflow.md
/contract-check disabled     # Contract tests excluded from default builds
/contract-check <service>    # All checks scoped to one service

Setup

On first run, ensure the script symlink exists:

ln -sfn "$SKILLS_DIR/contract-check/scripts/contract-check.sh" ./scripts/contract-check
chmod +x ./scripts/contract-check

Where $SKILLS_DIR resolves to ${CLAUDE_HOME:-$HOME/.claude}/skills.

Instructions

Step 0: Ensure Setup

Check that ./scripts/contract-check exists and is executable. If not, create the symlink as shown in Setup above.

Step 1: Parse Subcommand

Parse the user's argument:

• (none) or full → Run all checks (mechanical + semantic)
• status → Run all checks but only show the summary table
• stale → Run ./scripts/contract-check stale
• uncommitted → Run ./scripts/contract-check uncommitted
• sync-gaps → Run ./scripts/contract-check sync-gaps
• coverage → Run ./scripts/contract-check coverage (CI verifies each synced pact?)
• missing → Run semantic Missing Consumer Tests check (Step 3)
• docs → Run semantic Documentation Drift check (Step 4)
• disabled → Run semantic Disabled Tests check (Step 5). coverage is the mechanical companion: it catches commented-out PACTCONSUMER entries in a provider's CI verify job.
• <service> → Run all checks scoped to that service
• matrix → Run ./scripts/contract-check matrix