ENGINEERING
Audit Figma renames for broken Code Connect links and file GitLab issues
On a schedule, scans recently renamed Figma components, flags any whose Code Connect mapping now points at a missing or stale code path.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionList Figma components renamed since last runFigma
- ActionRead Code Connect map and verify source path in repoGitLab
- LogicKeep only missing or mismatched mappings
- ActionGet Code Connect suggestions for the correct mappingFigma
- OutputFile a GitLab issue per broken link with the fixGitLab
What it does
Periodically reconciles your Figma library against its Code Connect mappings. For every component renamed since the last run, it checks whether the mapped code source still exists and matches; broken or stale links become GitLab issues with the suggested corrected mapping attached.
When to use it
Use this as a safety net for design systems where renames happen faster than developers can relink. It catches mappings that silently rot after a refactor, so designers never hand off a component whose `get_code_connect_map` points nowhere.
How it works
- 1A daily schedule kicks off the audit.
- 2Pull Figma metadata for the library to list components renamed since the last checkpoint.
- 3For each, read its Code Connect map and confirm the `codeConnectSrc` path resolves in the GitLab repo.
- 4Branch: route only the entries with missing or mismatched sources forward.
- 5Get Code Connect suggestions to compute the most likely correct component and path.
- 6Open one GitLab issue per broken link, including the old mapping and the suggested fix.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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.