ENGINEERING
License-Compliance Gate on New PR Dependencies
When a pull request changes a lockfile, this scans every newly added dependency for its license and posts a pass/fail compliance check back on the PR.
How it runs
The automated pipeline, trigger to output.
- TriggerPR opened or synchronizedGitHub
- LogicDiff lockfile for newly added dependencies
- ActionResolve each package's SPDX license from registryGitHub
- LogicClassify licenses against allowlist
- OutputPost commit status + summary comment on PRGitHub
What it does
Watches pull requests that touch a dependency manifest or lockfile, identifies the packages that are newly introduced, looks up each one's license, and decides whether the PR is safe to merge. The verdict is written back to GitHub as a status check so the merge button reflects compliance.
When to use it
Use it on any repo where you must keep GPL/AGPL or unlicensed code out of a proprietary product, and you want the check to run automatically on every dependency change instead of relying on a reviewer to eyeball `package.json`.
How it works
- 1A GitHub PR event fires when the PR is opened or its commits change.
- 2A logic step diffs the lockfile to extract only the dependencies that did not exist on the base branch.
- 3For each new package, an action queries the registry metadata to resolve its declared SPDX license.
- 4A logic step classifies each license against an allowlist (permissive = pass, copyleft/unknown = fail).
- 5The final step posts a GitHub commit status and a summary comment listing each package and its verdict, blocking merge on any failure.
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.