🎯 The Problem
As developers, we spend hours crafting Pull Requests: writing descriptions, explaining why the change matters, and documenting code.
But once the PR is merged… it often disappears into the void.
That effort rarely lives beyond GitHub.
I’ve always felt this was a wasted opportunity.
Every PR — especially in open source — tells a story: the problem, the reasoning, the solution.
Why not turn that into something more lasting, like a blog post?
💡 The Solution: devtopost
That’s why I’ve been working on devtopost, a small side project that automatically turns your GitHub PRs into polished blog posts.
- Paste a PR link
- The tool analyzes the title, description, commits, and diff
- It generates a professional, markdown-ready article (introduction → problem → solution → impact → conclusion)
So instead of staring at a blank page, you already have a structured draft you can publish on your blog, dev.to, or LinkedIn.
🛠️ How It Works
Under the hood:
- GitHub API to fetch PR metadata & diff
- AI (LLM) to generate structured technical writing
- Opinionated prompts to enforce professional tone, Markdown formatting, and code snippet rules
The current MVP just lets you try it out with 1 free PR → blog conversion.
Later I’m thinking of offering subscriptions for people who publish frequently.
🤔 Why I’m Sharing This Here
I don’t want this to be an “ad”.
I’m genuinely curious:
- Would you use something like this?
- Do you see this as useful for open source maintainers who want to highlight their contributions?
- Or for engineers building a portfolio without rewriting the same stories?
I’d love feedback from this community — whether it’s “I’d never use it” or “here’s what could make it better”.
🚀 Try It
If you’re curious, you can try the MVP here:
👉 https://devtopost.ai
Thanks for reading!
Building this has been fun, but I want to make sure it actually solves a real pain point for devs.
Any feedback, feature requests, or even brutal honesty is welcome ✌️
Top comments (0)