ENGINEERING
Verify consumer contracts against a proposed spec change
When a provider opens a spec-change PR, replay every registered consumer contract against the proposed schema and block the merge if any consumer's expectations would break.
How it runs
The automated pipeline, trigger to output.
- TriggerSpec-change pull request openedGitHub
- ActionFetch proposed spec and consumer contractsPostgres
- ActionReplay each consumer contract against specShell
- LogicAny consumer contract failing?
- ActionPage provider on-call on failurePagerDuty
- OutputSet blocking or passing commit statusGitHub
What it does
Runs consumer-driven contract verification on spec changes. It collects the contracts each consumer has registered (the requests they send and responses they expect), validates them against the proposed provider spec, and fails the check the moment a consumer expectation is no longer satisfiable.
When to use it
Use this when you practice consumer-driven contracts and need provider-side enforcement: the provider should not be able to merge a spec change that silently breaks a known consumer. It complements unit tests by checking real, registered expectations rather than assumptions.
How it works
- 1A pull request touching the spec triggers the run from GitHub.
- 2The flow fetches the proposed spec and pulls all registered consumer contracts from a Postgres registry.
- 3A shell step replays each contract against the proposed spec and records pass or fail.
- 4A logic branch checks for any failed contract.
- 5On failure it sets a blocking commit status on the GitHub PR and pages the provider on-call via PagerDuty with the failing consumers.
- 6On success it sets a passing status.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.