ENGINEERING
Auto-assign PR reviewers by changed files and load
When a pull request opens, picks the best reviewers from the touched code areas, balances against each reviewer's current open-review load.
How it runs
The automated pipeline, trigger to output.
- TriggerPR opened or marked ready for reviewGitHub
- ActionFetch changed file paths for the PRGitHub
- LogicMap paths to reviewer pools and rank by open-review load
- ActionAssign two lightest-loaded reviewersGitHub
- OutputDM each reviewer the PR link in SlackSlack
What it does
Every new pull request gets routed to the right people automatically. The workflow reads which files the PR touches, maps those paths to owning reviewers, then weighs each candidate's current open-review backlog so nobody gets buried. It assigns the two lightest-loaded qualified reviewers on GitHub and pings them in Slack.
When to use it
Use it when CODEOWNERS alone keeps dumping reviews on the same one or two senior engineers, or when reviews stall because nobody was explicitly tagged. Good for teams of 5-40 where ownership is roughly known but load balancing is manual.
How it works
- 1A GitHub webhook fires when a pull request is opened or marked ready for review.
- 2The flow pulls the PR's changed file paths and matches them to an ownership map of code areas to reviewer pools.
- 3It queries each candidate's count of currently assigned open reviews and ranks them by lightest load.
- 4The top two qualified reviewers are assigned to the PR via the GitHub API.
- 5A Slack direct message notifies each assigned reviewer with the PR title, author, and a deep link.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.