ENGINEERING
PR gate for removed Figma components via GitLab and Slack
On each merge request, checks whether new code references Figma components that have been deprecated or removed from the library.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab merge request openedGitLab
- ActionFetch deprecated/removed components from FigmaFigma
- LogicScan MR diff for stale references; pass/fail gate
- ActionPost blocking GitLab review commentGitLab
- OutputPing MR author in SlackSlack
What it does
Stops drift before it merges. When a GitLab merge request opens, the workflow scans its diff for references to component names that Figma has deprecated or deleted, and if it finds any it posts a blocking review comment listing them and pings the author in Slack.
When to use it
Use this as a guardrail on active repos where the design system is still moving. Rather than cleaning up stale component usage in a later sweep, you catch it at the point of introduction, when the author still has context.
How it works
- 1A GitLab merge-request-opened event triggers the workflow.
- 2Pull the current deprecated and removed component list from Figma.
- 3Scan the MR diff for references to any of those names.
- 4A logic gate decides pass or fail based on whether stale references were found.
- 5On failure, post a blocking GitLab comment enumerating the offending lines.
- 6Ping the MR author in Slack with a link; on pass, exit quietly.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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
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.