DOCUMENT OPS
Block PRs whose README code examples no longer compile
On every pull request that touches a README, extracts the fenced code blocks, compiles and runs them in a sandbox.
How it runs
The automated pipeline, trigger to output.
- TriggerPull request opened or synchronizedGitHub
- LogicOnly continue if a Markdown file changed
- ActionExtract fenced code blocks from changed READMEsGitHub
- ActionCompile and run each block in a sandboxShell
- LogicAggregate results into pass or fail
- OutputPost blocking GitHub check on the PRGitHub
What it does
Turns your README code samples into a merge gate. When a pull request changes any Markdown doc, this workflow pulls every fenced code block, runs it in an isolated shell, and reports a single GitHub status check. A broken example fails the check, so drift never reaches the default branch.
When to use it
Use it on any public-facing library or SDK where the README is the first thing users copy-paste. If "the quickstart doesn't even run" would be an embarrassing issue to receive, gate it here.
How it works
- 1A pull request is opened or updated on GitHub.
- 2A filter checks whether any `*.md` file changed; if not, the run exits clean.
- 3The workflow fetches the changed Markdown and extracts every fenced code block tagged with a runnable language.
- 4Each block is written to a temp file and executed in a sandboxed shell with the repo's install step first.
- 5Results are aggregated into one pass/fail summary and posted back as a GitHub commit status check that blocks merge on failure.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 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 Document Ops workflows
Narrate new Dropbox PDFs into MP3 audio versions
When a PDF lands in a watched Dropbox folder, extract its text and generate an ElevenLabs voice narration.
On-demand PDF narration via webhook with emailed audio link
Accepts a PDF URL through a webhook, generates an ElevenLabs narration with the requested voice, stores the MP3, and emails the requester a download link.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Batch-narrate a Google Drive PDF folder in multiple languages
On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…
Executed Contract Exhibit & Initials Completeness Gate
When a signed contract lands in a Dropbox intake folder, verify every required exhibit, schedule, and initialed page is present.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
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.