blog.bumper
A second push, on autopilot. Your coding agent already writes the report — blog.bumper turns it into a published post the moment you're done.
Overview
Most dev blogs die at the second push: you finish the work, you ship it, and then you're supposed to stop and write about it. blog.bumper removes that step. Your agent drops a structured report into a chat channel; blog.bumper reads it, renders it into a validated MDX post, commits it to your blog repo, and pushes — your host builds it live.
It's deliberately loosely coupled. blog.bumper triggers off a chat message, never your build, so a failure can't break your work and a skipped report just means there's nothing new to post. There's no AI summarization in the loop — the report is already structured, so every post is deterministic and yours.
Built around swappable roles — a chat source, an agent, a content repo, a host — so the system survives change. Today it runs Discord → Claude Code → GitHub → Vercel, with Telegram and other adapters on the way.
Key concepts
- Reads structured end-of-task reports from a chat channel
- Injection-safe by design — report content rendered as data, never executed
- Deterministic output — same report, same post, no paraphrasing
- Review-branch flow — a human glance before anything goes live
- Idempotent and fast-forward-guarded — safe to run on a schedule
- Open source, MIT licensed, built to be forked and extended
Demo
