Built a tool that turns your GitHub commits into build-in-public posts

Name: Built a tool that turns your GitHub commits into build-in-public posts
Availability: InStock
Author: TedOS

by TedOS·Mar 1, 2026·7 points·2 comments

Visit Project View on HN

AI Analysis

●●SolidSolve My ProblemDark Horse

Solves the actual problem: generating post ideas instead of blank-page paralysis.

Strengths

•Tone preservation—reads your voice from past commits and Twitter posts, not corporate-fied templates
•Addresses upstream friction (ideation) rather than downstream (scheduling), which existing tools ignore
•One-click multi-platform publishing cuts 6+ hours of weekly content work for active shippers

Weaknesses

•Relatively small audience—only works for devs who ship frequently and care about public visibility
•AI drafting accuracy depends entirely on commit quality; bad commits = bad posts

Post Description

I kept failing at building in public for the same reason every time: not fear of judgment, just the blank page after a long day of shipping.

Something always happened. But converting "refactored auth flow" or "fixed that edge case that's been annoying me for a week" into something worth posting felt like a second job on top of the actual job. So I'd skip it. Then skip it again. Then stop entirely.

The approach: connect your GitHub, it pulls recent commits and repo activity, and generates draft posts for multiple platforms in your tone — raw founder voice, not content creator polish. The idea is you're always starting from something real you actually did, not staring at a blank box trying to manufacture insight.

A few decisions I made consciously:

Didn't want to build another scheduler. Hypefury/Typefully solve distribution. This solves the upstream problem: knowing what to say in the first place.

Kept the output editable and minimal — 2-3 options per session, short, easy to tweak. Not trying to automate your voice, just unblock it. Free tier to start. Wanted real usage before charging anyone.

Still early. Roadmap includes better tone calibration, tighter commit parsing, and more platform targets. But I've been using it daily myself which is the real test. Would love feedback, especially from anyone who's tried and failed at BIP consistency before.