ENGINEERING
Copyleft Detection Incident Auto-Block
When a PR introduces a strong-copyleft license (GPL/AGPL), this immediately fails the check, requests changes on the PR.
How it runs
The automated pipeline, trigger to output.
- TriggerPR opened or synchronizedGitHub
- ActionResolve added dependency licensesGitHub
- LogicDetect strong-copyleft (GPL/AGPL) licenses
- ActionSubmit Request Changes reviewGitHub
- ActionOpen assigned Linear remediation issueLinear
- OutputLink Linear issue back into the PRGitHub
What it does
Treats a strong-copyleft dependency as a blocking incident rather than a soft warning. The moment one is detected on a PR, it converts the check to a hard failure, formally requests changes, and creates a tracked remediation task so the violation cannot be merged or forgotten.
When to use it
Use it when AGPL or GPL contamination is a serious legal risk for your codebase and you want a zero-tolerance, fully tracked response the instant such a dependency appears in review.
How it works
- 1A GitHub PR review event fires on open or synchronize.
- 2An action resolves the licenses of the PR's added dependencies.
- 3A logic step checks specifically for strong-copyleft SPDX identifiers; non-matches exit quietly.
- 4On a match, an action submits a GitHub Request Changes review naming the offending package.
- 5An action opens a Linear issue assigned to the PR author with the package, its license, and suggested permissive alternatives.
- 6The output step links the Linear issue back into the PR conversation.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.