ENGINEERING
Detect GraphQL schema breaking changes and file owner tickets in Linear
On a schema change PR, runs a GraphQL breaking-change check against the deployed schema, posts a summary to MS Teams.
How it runs
The automated pipeline, trigger to output.
- TriggerSchema-change PR openedGitHub
- ActionFetch proposed + production schemaGitHub
- LogicFind breaking changes, map to owning teams
- LogicStop if purely additive
- ActionOpen Linear issue per affected teamLinear
- OutputPost breaking-change digest to MS TeamsMicrosoft Teams
What it does
Guards a shared GraphQL schema. When a PR changes the schema, it compares against the live schema, finds breaking changes (removed fields, type narrowing, argument changes), maps each broken operation to the team that uses it via an ownership map, and creates a tracked Linear issue for that team plus a heads-up in MS Teams.
When to use it
You run a federated or shared GraphQL API where many clients query overlapping fields, and a single removed field can silently break a downstream app. Use this to convert breaking edits into accountable, assigned work.
How it works
- 1A PR touching the schema file triggers the flow.
- 2Fetch the proposed schema from the PR and the current production schema via GitHub.
- 3Run the breaking-change comparison and resolve each break to an owning team using the ownership map.
- 4Branch: stop if the change is purely additive.
- 5Open a Linear issue per affected team with the broken operation and PR link.
- 6Post a consolidated breaking-change digest to the platform MS Teams channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect Microsoft TeamsChannels, chats, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.