ENGINEERING
Sync HuggingFace watchlist from GitHub model references
On every push to your main repo, scans the code for HuggingFace model ids actually referenced.
How it runs
The automated pipeline, trigger to output.
- TriggerPush to default branchGitHub
- ActionExtract HuggingFace model ids from repo treeGitHub
- ActionLoad current watchlist from PostgresPostgres
- LogicReconcile adds and removals
- ActionWrite updated watchlist to PostgresPostgres
- OutputPost watchlist changes to SlackSlack
What it does
Keeps the model watchlist honest. Instead of maintaining a manual list, it triggers when your repository changes, greps the codebase for HuggingFace model identifiers (in configs, model loaders, env defaults), and reconciles those against the stored watchlist. Models newly referenced get added; models no longer referenced anywhere get retired. The result is a watchlist that always reflects what your code really loads.
When to use it
Use it when model usage shifts often and a stale watchlist means you either alert on models you dropped or miss models you quietly adopted. This is the upstream feeder for the other drift monitors in this catalog.
How it works
- 1A push to the default branch triggers the workflow via GitHub.
- 2It fetches the changed repository tree and extracts every HuggingFace model id pattern.
- 3It loads the current watchlist from Postgres.
- 4A reconcile step computes additions and removals.
- 5It writes the updated watchlist back to Postgres and posts a short summary of adds/removes to Slack.
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 SlackChannels, DMs, threads, mentions.
- 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.