ENGINEERING
Agent relinks renamed Figma components and raises a GitHub PR
An agent takes a renamed Figma component, finds the best-matching code component in the GitHub repo, updates the Code Connect mapping, edits the Code Connect source file.
How it runs
The automated pipeline, trigger to output.
- TriggerChat request with renamed node URL
- ActionRead Code Connect map and Figma metadata for the nodeFigma
- ActionSearch GitHub repo for the renamed componentGitHub
- ActionWrite corrected Code Connect mapping to FigmaFigma
- ActionEdit source file and commit to a branchGitHub
- OutputOpen GitHub PR and report back in chatGitHub
What it does
Gives an autonomous agent the job of healing a single design-to-code link. Pointed at a renamed Figma node, it reasons over the codebase to identify the renamed component, updates the Code Connect mapping in Figma, edits the corresponding source file, and opens a GitHub pull request describing what changed and why.
When to use it
Reach for this when the correct code target isn't a trivial 1:1 rename — for example a component was split, moved between packages, or renamed alongside prop changes. The agent's judgment beats a deterministic find-and-replace.
How it works
- 1A chat or manual trigger supplies the renamed Figma node URL.
- 2The agent reads the node's current Code Connect map and Figma metadata.
- 3It searches the GitHub repo to find the renamed or relocated code component.
- 4It writes the corrected Code Connect mapping back to Figma.
- 5It edits the Code Connect source file and commits to a new branch.
- 6It opens a GitHub pull request and posts the summary back in chat.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.