ENGINEERING
Loom Review Blocking-Changes Gate on GitHub
Transcribes a reviewer's Loom walkthrough, detects whether they requested blocking changes.
How it runs
The automated pipeline, trigger to output.
- TriggerLoom review recording publishedLoom
- ActionFetch transcript from LoomLoom
- ActionClassify verdict and extract change requestsOpenAI
- LogicBranch: blocking vs. non-blocking
- OutputSubmit GitHub review (request changes or approve)GitHub
What it does
Reads a reviewer's spoken Loom code review and converts the verdict into a real GitHub review state. If the reviewer voiced blocking concerns, the flow submits a formal 'Request changes' review listing each item; if not, it submits an approval. The PR status reflects the spoken decision automatically.
When to use it
Use it when video reviews need to actually gate merges. Stops the common gap where a reviewer says 'this needs work' on camera but never clicks the button, leaving the PR mergeable.
How it works
- 1A Loom webhook fires when a review recording is published with the PR URL in its metadata.
- 2The flow pulls the transcript from Loom.
- 3OpenAI classifies the review as blocking or non-blocking and extracts the specific change requests as a list.
- 4A logic branch routes on the classification.
- 5GitHub submits either a 'Request changes' review containing the extracted items, or an 'Approve' review, then posts the Loom link as context.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.