DOCUMENT OPS

Turn merged API changes into suggested ReadMe edits

When a PR labeled api-change merges, an LLM reads the diff and the affected ReadMe pages.

CategoryDocument Ops
EngineSim + Paperclip
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • Triggerapi-change PR mergedGitHubGitHub
  • ActionFetch merged diff and affected endpointsGitHubGitHub
  • ActionRead current affected ReadMe pagesReadMeReadMe
  • ActionDraft page-specific doc edits with LLMOpenAI
  • OutputSave edits as ReadMe drafts for reviewReadMeReadMe

What it does

Closes the gap between shipping an API change and writing the docs. On merge of an api-change PR, it feeds the code diff and the matching ReadMe pages to an LLM that produces concrete, page-specific edit drafts — new parameters described, removed fields struck, sample requests updated.

When to use it

Use it when writing docs is the bottleneck, not knowing they need writing. This produces a reviewable first draft so doc owners edit and approve instead of starting from a blank page.

How it works

  1. 1A GitHub pull_request closed-and-merged event with the api-change label triggers the flow.
  2. 2The workflow fetches the merged diff and identifies which documented endpoints it touches.
  3. 3It pulls the current content of the affected ReadMe pages.
  4. 4An OpenAI step drafts precise edits for each page, grounded in the diff and existing copy.
  5. 5It creates the updated page content as a draft in ReadMe and notifies the doc owner to review and publish.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect ReadMeAPI docs, changelog, auth.
  3. 3
    Connect OpenAIModels, embeddings, files.
  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.