OP here. I've been trying to "build in public" recently, but I found that switching context from VS Code to Twitter/X just to write "Fixed a race condition" felt like friction. I often ended up posting nothing because translating code-diffs to human-readable text takes more mental energy than fixing the bug.

I built Git to Tweet to automate this loop.

How it works:

It hooks into your GitHub repo (via OAuth).

It pulls the metadata and diff summaries of your recent commits.

It passes the diff through a specifically tuned prompt (to avoid generic "AI slop") that extracts the intent of the code change rather than just listing file names.

It generates a draft that you can edit before posting.

The Tech Stack:

Frontend: React + Framer Motion (spent way too much time on the "terminal" animations you see on the landing page).

Backend: Node.js/Supabase.

LLM: Currently testing models to see which is best at understanding code context without hallucinating features.

The landing page includes an interactive simulator (hardcoded scenarios for now) if you want to see how the "translation" logic works without connecting a repo.

I’m curious if others find this "translation" layer useful, or if you prefer manual changelogs? Feedback on the diff parsing accuracy would be awesome.

URL: https://landkit.pro/git-to-tweet