How I stopped manually posting to 6 platforms and built an automated PR pipeline for my side projects

When you're a solo developer with a day job, actually building the project is maybe 60% of the work. The other 40%—the part nobody talks about—is getting anyone to notice it exists. And honestly, that 40% is where most of us fall apart. My usual pattern: ship something, post about it once on Twitter, maybe write a Qiita article if I'm feeling ambitious, get distracted by the next thing, and watch the project quietly die with 12 GitHub stars. The problem isn't motivation. It's friction. Writing a technical article for Qiita, reformatting it for Dev.to, condensing it to 280 characters for Twitter, crafting a Reddit post that doesn't get immediately downvoted—each platform has different norms, different formats, different audiences. Doing all of that manually for every project update is genuinely exhausting, and when it competes with actually writing code, it loses every time. So last year I started building tooling to automate this. Along the way I hit a bunch of interesting technical pr