case 07

Repo Pulse

Your repo's week, as a video — from live data, on a schedule.

// the problem

Every active repository generates a weekly story — commits landed, contributors showed up, something notable shipped — and almost nobody tells it, because telling it is manual: pull the numbers, make the charts, lay out the post. Maintainers who want a changelog with a pulse, and devrel teams who want something watchable to post, end up doing design work every single week or not doing it at all.

// how everyone solves it

By hand, when at all: query the GitHub API into a spreadsheet, screenshot some charts, arrange them in a slide or a canvas tool, export. The polished version — an animated motion-graphics recap — costs an editor’s afternoon per issue, so it happens for launches and never for week 37. Either way the result isn’t reproducible: next week starts from zero, and no cron job can run a design tool.

// the m0saic program

@m0saic/github/weekly-pulse/v1 is the whole pipeline in one template: a fetcher pulls the repo’s week from the GitHub API, an adapter derives the pulse sheet, and eight animated beats — title, KPIs, activity trend, top contributors, changes breakdown, notable commits — cross-fade into one deliverable. Data in, video out; the render is deterministic, so the same week’s data always produces the same video. Which means the thing nobody’s weekly recap ever was: cron-able.

a weekly pulse render — eight beats of a repository's week, from live datathe same render lineage as the m0saic.io homepage hero

// run it yourself

One command, straight from a terminal. The CLI carries the template, the engine, and the validator — if the layout can’t render correctly, it fails before a single frame is written.

npx m0saic pulse --repo owner/name

// read the source

The template behind this study is @m0saic/github/weekly-pulse/v1 — a typed, unit-tested program, not a script. The template library is headed for open release; the m0saic source lives on GitHub.