At Biel.ai, we have a new AI teammate called Nova. One of its jobs is keeping the documentation up to date.
In one PR, it picked up a gap in our React integration guide. The package provided three components, but the instructions only covered one.
Nova added the missing search-widget and embedded-chat sections, including installation steps and code examples. It also updated the introduction and linked to our existing embedded-mode documentation.
We reviewed the update in the PR and merged it:
This is how the workflow runs. Nova checks merged pull requests and recent commits on main, reads the changes, and compares them with our docs. When it finds documentation work, it opens a follow-up PR.
That might be an undocumented property, instructions that no longer work, or a missing guide. Its updates can include screenshots too.
We correct the draft and ask for changes in the PR. Nova handles the recurring investigation: inspecting product changes, finding affected pages, and proposing what readers need to know.
Checking beyond recent changes
Nova also reviews the codebase against the documentation once a week, independently of the recent-change checks.
This covers gaps that are not connected to a new commit. Nova records which areas it has reviewed so successive runs can cover new ground.
Findings arrive as PRs, just like updates from the commit checks. Nova can finish a run without opening anything if it finds no documentation work.
What we are still correcting
Nova follows our style guide, but weāre still refining its instructions. We need to be clearer about which codebase details belong in public documentation and which should stay internal.
It also needs to distinguish a reference update from a guide. A technically correct draft can still need substantial restructuring if it uses the wrong format.
Then thereās the AI slop: repeated explanations, generic advice, and paragraphs that add length without helping the reader. Weāre refining the instructions to favor direct answers, concrete examples, and the steps someone needs to complete the task. Sometimes the most useful correction is deleting a paragraph.
We use those review corrections to improve future drafts. Having Nova handle recurring checks leaves more time for work I want to focus on: improving difficult guides, explaining workflows, and keeping the docs easy to navigate as the product grows.
Have you tried automating documentation maintenance? Reply and tell me what worked. But especially what didnāt!




So great, so interesting, so cool
Please may I come work with/for you?! I canāt get my teams to do docs-as-code and very much want to learn. Iām working with our AI R&D group on a prototype that finds and helps fill gaps in doc but itās not automated