ENGINEERING

Loom Walkthrough to Structured PR Review Notes

When a reviewer records a Loom code walkthrough and links it on a GitHub PR, this transcribes the video and posts a structured review summary as a PR comment so the notes are…

CategoryEngineering
Enginesim
Difficultyintermediate
Triggerwebhook
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerLoom recording completed (webhook)LoomLoom
  • ActionFetch Loom video transcriptLoomLoom
  • ActionSummarize transcript into structured review notesOpenAI
  • OutputPost review notes as PR commentGitHubGitHub

What it does

Turns an informal Loom screen recording into durable, written review notes attached directly to the pull request. The spoken walkthrough is transcribed, summarized into actionable points, and posted as a GitHub PR comment so future readers do not have to rewatch a video.

When to use it

Use it when your team prefers async code review by video but you still need the substance captured in writing for the PR record, onboarding, or audit. Ideal for teams where senior reviewers explain context faster by talking than by typing.

How it works

  1. 1A Loom recording finishes processing and fires its webhook, carrying the video URL and the PR link from the recording title or description.
  2. 2The flow fetches the Loom transcript text via the Loom API.
  3. 3OpenAI condenses the transcript into structured notes: a summary, a bulleted list of concerns, and explicit requested changes.
  4. 4A GitHub action posts the formatted notes as a review comment on the target PR, with a link back to the original Loom for full context.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LoomVideo transcripts, libraries.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GitHubRepos, issues, pull requests, actions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.