ENGINEERING
Block PRs that introduce OpenAPI breaking changes
On every pull request, diffs the committed OpenAPI spec against the base branch, classifies breaking changes.
How it runs
The automated pipeline, trigger to output.
- TriggerPR opened or updated touching openapi.yamlGitHub
- ActionFetch PR spec and base-branch specGitHub
- LogicDiff specs and classify breaking vs additive
- LogicAny breaking changes found?
- OutputPost pass/fail status check and inline commentGitHub
What it does
Guards your API contract at the source. Whenever a pull request touches the OpenAPI spec, this workflow compares the new spec to the version on the base branch, flags backward-incompatible changes (removed endpoints, deleted fields, tightened types, new required parameters), and writes the verdict back to GitHub as a commit status and a review comment.
When to use it
Use it when you publish or consume an OpenAPI spec checked into a repo and want a hard gate so no one accidentally ships a breaking change. Ideal for teams enforcing semver on their API.
How it works
- 1A pull request event fires when the spec file changes.
- 2The workflow fetches both the PR version and the base-branch version of the spec from GitHub.
- 3A diff step computes the structural delta between the two specs.
- 4A classifier decides whether any change is breaking versus additive.
- 5If breaking, it posts a failing status check and an inline PR comment listing each violation; if clean, it posts a passing check.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.