introducing: Auto Knowledge Gap Finding for Your Docs Your docs probably don't know what shipped, and no one remembers to keep them up to date. Every release creates the same cleanup job: search the docs, decide what is missing or stale, find the evidence, and write the update. Most... teams discover the gap when a customer asks a question the docs should have answered. So we built Knowledge Gaps in Compare GitHub releases, RSS feeds, or changelog entries against your customer and internal documentation. See missing, stale, hard-to-find, and needs-triage findings with the release evidence and every documentation page BuildBetter checked. Approve the real work, copy a ready-to-use prompt into your agent, or attach the finding to a project. Happy building!show more

finally docs that dont rot

Automating the process of fixing stale internal documentation is absolute galaxy brain

Solving the good good

Great project man, I love it. Also, beautiful mustache 🥸

Fred Brooks named it in 1975. Documentation is a shadow of the code, always a step behind reality. The fix is not writing more. It is closing the loop between what shipped and what the docs claim shipped.

Well said

docs rotting after every release is a constant nightmare

consider me the nightmare killer

docs rot is real

This seems like a common problem for many teams.

if you had to show one video to prove x is worth it, would this be it

Docs drifting after every release is too real

updating docs after every release is such a tedious hunt

docs maintenance sucks

Looks neat, would love to see more updates!

needed a reminder that perfection exists, so i'm bringing this back to the tl...

this is huge, finally a tool that catches doc gaps before customers do instead of after

Maintaining documentation usually falls behind the moment the first pull request is merged.

This is such a real problem. Docs always lag behind what actually happened. Would love to see this catch things before a customer does. Hope it works with messy wikis too.

We integrate with a lot of changelog tools as well as having our own but we built a custom scraper that can work off of basically as messy of the documentation as you can imagine

ngl this is such a real pain point, the docs always end up being the last thing anyone thinks about 😅

now it can be something no one has to think about 😉

Eliminating doc debt automatically is huge. Game changer for dev teams!

Docs going stale, real pain point.

every release makes docs stale and nobody tracks what changed

this hits home, docs always play catch-up with the code 😅 nice tool, will poke around soon!

Nghe hay đấy, nhưng không biết nó có tự tìm được các tài liệu nội bộ của mình để cập nhật không nhỉ? 🤔

@PersusMichaels

Chắc mình cũng nên quét thử mấy tài liệu cũ của team xem có lỗ hổng nào không 😂📄

finally fixing doc rot

This solves a real pain point! 🤖📚 Keeping docs updated just got smarter. 🚀🔥

Docs rot because writing them sits outside the definition of done, not because nobody can find the gaps — teams generally know which pages are stale. The interesting bet here is that a queue of pre-approved diffs is cheap enough to clear that the incentive finally flips; the failure mode is 496 findings nobody triages, which is just a second backlog with better evidence attached.

docs get stale fast i wish releases updated them automatically

Chức năng này hay quá, tài liệu của mình cũng đang cần một công cụ như vậy đó! 📄

Chức năng này nghe hữu ích thật, chắc sẽ đỡ tốn thời gian rà soát tài liệu lắm 😊

Docs rot because writing them is unowned work that never blocks a release — the gap was always visible, just never anyone's ticket. Turning it into a queue with evidence attached is the actual product; detection was never the hard part, assignment was.