ENGINEERING
Auto-map affected modules on a GitLab merge request
When a merge request opens, it inspects the changed files, groups them into the modules and owning teams they touch, and posts a clear affected-module map as an MR note.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened or updated webhookGitLab
- ActionFetch changed files for the MRGitLab
- ActionClassify files into modules and ownersShell
- LogicDedupe modules, flag high blast radius
- OutputPost affected-module map as MR noteGitLab
What it does
Every time a merge request is opened or updated, this workflow reads the MR diff, maps each changed file to a logical module (using your repo's directory-to-module rules), and posts a tidy note listing which modules and owning teams the change touches. Reviewers see blast radius at a glance instead of scrolling raw file lists.
When to use it
Use it on any monorepo or large service where file paths don't obviously map to ownership, and where reviewers waste time figuring out what a change actually affects. Especially useful when CODEOWNERS alone isn't expressive enough.
How it works
- 1A GitLab merge-request webhook fires on open/update.
- 2The workflow fetches the list of changed files for that MR via the GitLab API.
- 3A shell step runs your path-to-module rules to classify each file into a module and owning team.
- 4A logic step deduplicates the modules and flags any change that crosses more than three modules as high blast radius.
- 5It posts a formatted affected-module map as a note on the MR, tagging the relevant team handles.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 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.