CHATBOTS

/improvedocs: draft a ReadMe edit and open a GitHub PR

When a teammate runs /improvedocs in Slack with a correction, the agent finds the relevant ReadMe page, drafts the revised Markdown.

CategoryChatbots
Enginepaperclip
Difficultyadvanced
Triggerwebhook
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack /improvedocs slash command receivedSlack
  • ActionFind target page via ReadMe searchReadMeReadMe
  • ActionDraft revised Markdown section with OpenAIOpenAI
  • LogicConfirm single page matched before PR
  • ActionOpen GitHub pull request with the editGitHubGitHub
  • OutputPost PR link to SlackSlack

What it does

Turns a casual Slack correction into a reviewable docs change. A user runs `/improvedocs` describing what's wrong or missing; the agent locates the right ReadMe page, generates a clean Markdown edit grounded in the existing content, and opens a GitHub pull request in your docs-as-code repo. Nothing publishes automatically — a human approves the PR.

When to use it

When your ReadMe docs are synced from a Git repo and you want frontline staff to propose fixes without learning Git. Ideal for capturing tribal knowledge the moment someone spots a stale or wrong page.

How it works

  1. 1Slack sends the `/improvedocs` slash-command text to the webhook.
  2. 2ReadMe search identifies the page most likely needing the change.
  3. 3OpenAI rewrites the relevant section as a focused Markdown diff.
  4. 4A logic step confirms a single target page was matched before proceeding.
  5. 5A GitHub pull request is opened with the edit and the requester's note.
  6. 6The bot posts the PR link back to Slack for review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect ReadMeAPI docs, changelog, auth.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect GitHubRepos, issues, pull requests, actions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.