AI AGENTS
Loom dev walkthrough to GitHub docs PR
Converts a published Loom engineering walkthrough into a Markdown SOP and opens a pull request adding it to the repo's docs folder for code-review-style approval.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom video publishedLoom
- ActionFetch Loom transcriptLoom
- ActionConvert transcript to Markdown SOPHugging Face
- ActionCommit doc to new branchGitHub
- OutputOpen GitHub pull request for reviewGitHub
What it does
Takes an engineer's Loom walkthrough of a setup, deploy, or debugging process and turns it into a Markdown doc, then opens a GitHub pull request so the SOP gets reviewed and versioned like code.
When to use it
Use it for engineering teams that keep docs-as-code in the repo. When someone records how a service works or how to run a migration, this drafts the written version and routes it through your normal PR review instead of letting tribal knowledge stay in a video.
How it works
- 1A new Loom video in the engineering workspace triggers the flow.
- 2The agent fetches the recording transcript.
- 3A Hugging Face model converts the transcript into a clean Markdown SOP with code blocks, headings, and an embedded Loom reference.
- 4The agent creates a new branch and commits the file under the repo's docs directory.
- 5It opens a GitHub pull request titled with the SOP name, body noting it is an AI draft from a Loom recording pending human edits.
- 6Reviewers approve, edit, or reject through the standard PR flow.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 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 AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.