How Amendary works

When you ship, a sentence in your help center can stop being true, in every language. Amendary finds it, drafts the fix, and shows you the change that caused it. Here is the whole flow.

  1. 1

    Connect GitHub and your help center

    Install the Amendary GitHub App on the repos you choose. Amendary reads your code and never changes it. Then, on the Pages tab, add where your articles live: Notion, GitHub, Zendesk Guide or Intercom Articles.

  2. 2

    Pick what your articles follow

    On the destination's card, set what its help articles follow: a GitHub repo, or your public changelog. One repo can feed all four. Then choose the articles to keep correct. Translations come with their source article. Articles you do not pick are never read.

  3. 3

    Read what shipped

    Each day Amendary reads what shipped. From GitHub: releases, tags or commits, as you set per repo. From a changelog: each new entry, checked like a release. During setup you can run a first check and see the result right away.

  4. 4

    Review the fix in every language

    When a release makes a sentence wrong, Amendary drafts the fix for the source article and shows the change that caused it. It then carries the fix into each translation. Fixes wait in your Queue, grouped by release, one row per language. New teams start on Review first.

  5. 5

    Approve it, or undo it

    One approval updates every ready language. Published stays published and drafts stay drafts. You can dismiss one language alone. Undo writes the old text back, as long as nobody edited the article since.

Details for engineers

The same flow, with the mechanism: what is read, what is checked, what the model sees, what is held back, and how an edit reaches a page. Terms are defined in the glossary.

Connect

The GitHub App reads repository contents and metadata on the repos you share, so it can see what landed. A destination is where your articles or docs live: a Notion connection, a GitHub repo (its docs folder or wiki), a Zendesk Guide account or an Intercom workspace. Add one with Add destination on the Pages tab. A team can have several.

Each destination’s help articles follow one source of what shipped: a GitHub repo or a changelog URL, never both. One repo can feed several destinations at once, and each article is fixed once, in its own home.

Watch pages and map them

Connecting a destination only makes pages discoverable. A watched page gets an audience (Help center or Engineering docs), a type (Docs & guides, On-call runbook, Incident playbook, Architecture decisions, or Product updates) and a mapping to a repo. Unmapped pages are never read for a check and never edited. A help article follows its destination instead: it maps to the repo set there, or to no repo when it follows a changelog. Zendesk and Intercom articles are always Help center.

A Notion page can map to several repos. Each mapping is Describes this repo (its changes trigger checks) or Background only (no checks, unless you tick Check when this repo changes too). A GitHub page maps only to the repo it lives in. See Pages & mapping.

What triggers a check

Engineering docs are checked per landed commit on the default branch (a merged pull request or a direct commit). Help articles follow their destination’s source. For GitHub, that is the trigger set per repo: commits by default, or a branch, published GitHub Releases, or tags. For a changelog URL, it is each new dated entry, checked only against the articles that follow it. Open pull requests never trigger a check. Prose files in the repo (Markdown, docs, help, legal, marketing) are not treated as evidence of product behaviour.

What the model sees

For each change: a short summary, the changed paths and the diff (whole when it fits, otherwise the most relevant parts). For each mapped page: the page text, or the sections that match the change. Nothing from an unmapped page is sent. All of it is marked as untrusted content. The model rewrites a region of the page; code works out which blocks change.

Grounding

Hard values (versions, paths, URLs) in an edit must appear in the change or in the code after it. Soft values (bare numbers, Title Case phrases) are shown as “check these” and never hold a correction.

Review modes and holds

Review mode is set per audience in Settings. New workspaces start on Review first, and the free trial is always review-only. On a paid plan or with your own Anthropic key, an owner can switch an audience to Apply automatically. The Help center setting covers every help center.

In auto mode, five things still wait for a person: a hard value the change does not back up, a removed value the change does not mention, an edit that removes or shrinks content, a possible decision-record supersession, and an addition (except a fully grounded addition that rewrites a section and deletes nothing). A proposed new page always waits, as do “no edit drafted” and “the edit could not be planned”. See Queue & reviews.

Delivery

On Notion, a correction edits the affected blocks and keeps unchanged formatting. If the edit cannot be placed exactly, Amendary posts a page comment instead. On GitHub, it is a pull request (the default) or a commit, only where GitHub docs writing is on for that repo. A repo with it off is read-only. In a Markdown help center, every language of a fix lands in the same pull request. On Zendesk and Intercom, an approved fix updates the live article body in place. A published article stays published and a draft stays a draft. The write is refused if the article changed since the fix was planned.

Audit and undo

Each correction records the change summary and source link, the draft, the applied text and the text it replaced, in an append-only log. Raw diffs are not kept. Undo checks the block was not edited since, then restores the stored original. More in Security.

Runs you start on demand

Three more runs use the same connections. Each shows its credit estimate before it starts.

  • Generate docs: guides, runbooks, playbooks, decision records or a product-updates backfill from a repo, reviewed before publishing. In Zendesk and Intercom, new articles are saved as drafts. Product updates are Notion only.
  • Diagrams: one for each engineering page a generate run writes to Notion or a docs folder, or one you ask for on a Notion page. Every label is checked, and a suggested diagram waits in the Queue.
  • Cleanup: Keep or Probably remove for each article or page in any destination, from today’s code and the history of the repos you pick. It never edits a page.

These runs work in the background and resume after a server restart, with the credits they hold.

Try Amendary on your own help center

Connect Notion, GitHub, Zendesk or Intercom and pick the articles to watch. Your first check shows what Amendary would fix, with the change as proof.

Free for 14 days with no card, and every edit waits for your review. Or free forever with your own Anthropic API key. Code is never touched.