How do you keep documentation up to date with AI generated code?

Join the discussion

• Hacker News
• I pr and do regression test
  by jsabess24
• have an ai workflow man it’s mid 2026.

  any time ai does any work, it ensures the ADRs are up to date.

  it is part of the execution workflow.

  maintain the todos which are a record of work that was done. ADRs have the latest current documentation.

  by moomoo11
• The documentation lives alongside the code and is changed at the same time.
  by trio8453
• replace documentation for an agent/chatbot accessing a RAG with the collection of requirements/design docs plus the code repository. I have been doing a POC at my day job and it works surprisingly well even with SLMs ( Gemma3 4B, i smy current favourite )
  by slipwalker
• The same entity that generates the code generates the documentation. If you have 75% of your code generated by AI, then 75% should be documented by AI.
  by segmondy
• The 75% number matters less than the review loop: every AI-heavy PR still needs a human owner, reproducible tests, and docs explaining the behavior change.
  by PaiDxng
• If you want do it right:

  1. Update the documentation first, to describe the desired / expected behaviour.

  2. Followed by the code changes that implement the documented behaviour.

  PRs: for any behaviour change, feature addition etc: patch must include corresponding documentation updates. If not: reject.

  Iirc that was (still is?) OpenBSD's approach to keeping docs up-to-date.

  by RetroTechie
• From my observations - by accumulating technical debt faster than US and EU financial combined.

  If someone asks about the internals of the projects it is - you want the truth, you can't handle the truth.

  by ReptileMan