Every team has the same problem: code ships, docs don't follow. Not because anyone forgets — because updating docs after every PR is tedious, manual work that always loses to the next ticket. docpr fixes this with a GitHub Action. When a PR merges, LLM analyzes the diff, finds the documentation files that are actually affected, and opens a PR in your docs repo with the updates already written.
No reviews yetBe the first to leave a review for docpr.dev — docs that follow the code
Maker
📌
Hey PH! I work on a few open source projects and keeping docs in sync with the code is a constant losing battle. Every release something slips — a flag gets renamed, a config option changes, and the docs just quietly lie to people for months until someone opens an issue.
Built docpr to fix that for myself as up until know, I was doing that manually, but figured a Github action that watches every merged PR, figures out what changed, and opens a draft PR in the docs repo speeds up the process.
Code and docs at docpr.dev, would love to hear if others have the same problem.