Turn Your Git Commits Into Blog Posts — Automatically
CodeFlex analyzes your code changes, picks the right tone, and generates polished blog posts with AI — all from one CLI command.
Works with
Why Developers Love CodeFlex
Everything you need to turn code into content - built for developers who ship fast.
Smart Git Analysis
Automatically reads your commits, diffs, and file changes to understand exactly what you built.
AI-Powered Writing
Uses top LLMs via OpenRouter to generate polished, human-quality blog posts from your code changes.
Multiple Tones
Changelog, deep dive, casual, announcement, or technical — pick the voice that fits your audience.
Streaming Preview
Watch your blog post generate in real-time with a live streaming terminal preview.
Model Flexible
Switch between GPT-4o, Claude, Gemini, and more. One API, infinite possibilities.
One Command Setup
Just run npx codeflex generate. No config files, no boilerplate, no friction.
Three Steps to Ship Content
From git push to published blog post in under a minute. No context switching.
Push Your Code
Work as you normally do. Push commits, create tags, merge PRs. CodeFlex reads your git history automatically.
$ git push origin main
Counting objects: 14, done.
Writing objects: 100% (14/14), done.
Total 14 (delta 8), reused 0Pick Your Tone
Choose from 5 writing styles — changelog, deep dive, casual, announcement, or technical. Match your audience.
? Select tone for your post
❯ Changelog — bullet-style list
Deep dive — technical depth
Casual — conversational
Announcement — launch style
Technical — for developersGet Your Post
AI generates a polished blog post in seconds. Preview it live, tweak it if you want, then save or publish.
✓ Post generated (1,243 words)
## What's New in v1.3.0
We've been busy. This release brings
long-awaited dark mode support...
→ Saved: posts/2026-03-12-whats-new.mdWatch It Generate
Pick a tone and watch CodeFlex turn real commits into a polished post — live, right here.
All output above is pre-written for demo purposes. Real posts are generated from your actual commits.
How Much Time Will You Save?
Drag the slider to match how many posts you ship per week and see your time savings stack up.
Per Week
44h
≈ 6 full work days
Per Month
190h 31m
≈ 5 work weeks
Per Year
2288h
≈ 57 work weeks
That's time you could spend building, not writing. Get started free →
Ready to Ship Content
With Every Push?
Join the waitlist and be the first to turn your commits into blog posts.
Free while in beta • No credit card required • Unsubscribe anytime