Attio Contract Gate for CI

Overview

This skill turns an Attio integration change into deterministic pull-request evidence. It separates offline contract tests from an explicitly enabled read-only API smoke test.

Prerequisites

• A named repository and existing test runner
• Sanitized Attio response fixtures or generated contract fixtures
• A separately scoped CI credential only if a live smoke test is approved
• The endpoint's current required scopes and pagination contract

Tool Discipline

Use Read, Glob, and Grep to inspect workflows, fixtures, client code, and secret names. Use WebFetch only for current official Attio documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan.

Current Contract