Hey hunters! I'm Haim, solo dev behind ReadmeForge. Every repo I maintain has the same problem: the README describes the code as it was six months ago. So I built a GitHub Action + hosted API that fixes it automatically. How it works: on every push, the Action diffs the commit, sends the diff + current README to the API, and opens a PR with the updated README. Review-first — nothing lands without human eyes. There's a direct-commit mode if you want it. The part I'm proudest of: the Action is a thin client. Your repo never needs an AI API key — the key lives on my server. Every alternative I found makes you bring your own key (setup friction + another secret to leak). ReadmeForge needs zero config beyond the workflow file. Tech: composite action (bash + jq + curl), handles first-push, exits quietly when nothing doc-relevant changed, loop-guarded with a `[skip readmeforge]` marker. API is a Cloudflare Worker with per-repo monthly counters in KV. Pricing: free tier — 20 syncs/month, public repos, no signup. Pro is $9/mo via Gumroad: 1,000 syncs/month, private repos, direct-commit mode. Try it: https://github.com/marketplace/a... Site: https://readmeforge-app.netlify.... Would love your feedback — especially: is review-first PR the right default, or would you prefer direct commits?

ReadmeForge

README that updates itself on every push

README that updates itself on every push