adinsights-contract-guard

To classify API contract risk for integration changes, analyze prompts and changed files to determine touched surfaces and identify missing docs or tests. The tool produces a structured decision packet with rationale, evidence, and next actions for CI enforcement.

A contract decision packet is a machine-readable output containing contract_surfaces_touched, required_docs_updates, required_tests, reviewers, and next actions. It enforces CI strictness by evaluating breaking vs non-breaking changes across API, data, and integration surfaces.

To check if data contract changes are missing tests or documentation, analyze changed files and path hints against touched surfaces. The output flags missing required docs updates and required tests, providing rationale and next actions to resolve the gaps.

You can use contract risk classification to detect breaking integration contract modifications by evaluating path hints and changed files. It categorizes touched surfaces and returns a structured packet detailing whether the modifications break integration contracts.

Contract risk classification works with pyyaml dependencies for CI automation by enforcing CI-style strictness options. It analyzes prompts and changed files to output a machine-readable packet, ensuring API and data contract changes meet strict CI requirements.

Automated contract risk classification for API changes relies on analyzing prompts, changed files, and path hints to determine touched surfaces. It requires accurate file inputs and path hints to correctly identify missing docs or tests and enforce CI strictness.