ENGINEERING
Batch codemod for a Figma rename and ship one GitLab MR
Receives a Figma rename webhook, runs a repo-wide codemod to rename every code reference and update the Code Connect mapping.
How it runs
The automated pipeline, trigger to output.
- TriggerFigma rename webhook (old + new name)HTTP webhook
- ActionRead Code Connect map to resolve source pathFigma
- ActionRun codemod across the repo to rename referencesShell
- LogicAbort and alert if zero files changed
- ActionWrite updated Code Connect mapping to FigmaFigma
- OutputOpen GitLab MR with the full codemod diffGitLab
What it does
Turns one Figma component rename into a complete, repo-wide code change. It runs a codemod that renames every import, JSX usage, and the Code Connect source file across the GitLab project, refreshes the Figma Code Connect mapping, and packages everything into one merge request instead of scattered manual edits.
When to use it
Use it when a heavily-used component is renamed and the old name appears in dozens of files. The codemod guarantees consistency and the single MR gives reviewers one diff to approve rather than a trickle of follow-up commits.
How it works
- 1A Figma rename webhook delivers the old and new component names.
- 2Read the Code Connect map to resolve the old name to its repo source path.
- 3Run a shell codemod across the checked-out GitLab repo to rename all references.
- 4Branch: abort and alert if the codemod touches zero files (mapping likely wrong).
- 5Write the updated Code Connect mapping back to Figma.
- 6Open a GitLab merge request with the full codemod diff for review.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.