ENGINEERING
Route Dependency Release Notes to Affected Package Owners
When a watched dependency publishes a new release, determine which monorepo packages import it and notify each package's CODEOWNERS with a tailored summary of what changed…
How it runs
The automated pipeline, trigger to output.
- TriggerDependency release webhookHTTP webhook
- ActionFind consuming packages in dependency mapPostgres
- ActionResolve package owners from CODEOWNERSGitHub
- ActionWrite per-package change summaryOpenAI
- LogicOwner mapping exists?
- OutputSend tailored note to ownerMicrosoft Teams
What it does
Fans a single upstream release out to the right people in a monorepo. Rather than one broadcast message, it maps the dependency to each consuming package, reads CODEOWNERS to find each package's owner, and sends each owner a summary scoped to the APIs their package actually uses, so notices land only where they matter.
When to use it
For large monorepos where one shared dependency is consumed by many independently owned packages and a blanket "X was updated" announcement gets ignored. Use it to keep upgrade awareness targeted and low-noise.
How it works
- 1A release webhook fires for a watched dependency.
- 2The flow reads the monorepo's package-to-dependency map from Postgres to find consuming packages.
- 3It resolves each consuming package's owner from the CODEOWNERS file in GitHub.
- 4An LLM writes a per-package summary highlighting only the changed APIs that package imports.
- 5It branches on whether each package has a real owner mapping.
- 6It sends each owner a tailored release note via Microsoft Teams.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect OpenAIModels, embeddings, files.
- 5Connect Microsoft TeamsChannels, chats, files.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
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.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
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.