How docskoala works

Last updated Jul 3, 2026

What changed

DocsKoala watches the GitHub repositories you connect. Every time a pull request merges into your main branch, DocsKoala picks it up, decides whether it's worth documenting, and if so, drafts an article.

The pipeline, step by step

A pull request merges. GitHub notifies DocsKoala the moment it happens.
DocsKoala classifies the change. A fast AI model reads the PR title, description, and the list of changed files, then decides if this is something a customer would notice or care about. Internal changes (dependency bumps, refactors, test-only changes) are left alone and never reach a human.
DocsKoala checks for a related article. If your help center already has an article covering this area of the product, the draft becomes an update to that article instead of a brand-new one.
DocsKoala drafts the article. A more capable AI model writes the article, grounded in the actual code diff and the PR's title and description. It won't invent steps, UI text, or behavior the diff doesn't support.
The draft lands in your Review Inbox. You read it, edit anything that needs a human touch, and click Approve, Edit, or Dismiss.
On approval, the article publishes. It appears in your public help center and becomes available to the widget and search immediately.

Where to find it

Pending drafts live in your Review Inbox. Published articles appear in your help center under Articles, organized by category.

Things to know

A change that isn't customer-facing (an internal refactor, a dependency bump) typically never generates a draft at all.
You can also trigger the pipeline manually with a commit message that starts with /koala, for changes made without opening a pull request.
Nothing goes live without someone on your team clicking Approve.