your releases
deserve better than
a changelog.

A Claude Code skill and CLI that turns your project into a twenty-second launch video, then measures it before you post it.

one line, for claude code
$ npx @irvinosazee/shipreel skill install
★ star on github Free and open source, MIT. Needs Node 22+ and FFmpeg.

anything can make a video.

The question is whether you can post it without watching all twenty seconds first. shipreel measures every render and tells you what it found. This is the actual report from the video above.

A failed check names itself and why. The tool that produces these reports is covered by 297 tests, run on every change.

shipreel verify shipreel.mp4
  1. duration22.7swithin plan
  2. frame1080×1920vertical
  3. loudness−14.7 LUFSfeed-matched
  4. posterframe 0baked in
  5. type size42px minphone legible
  6. read time0.3s / wordheld long enough
  7. safe zone1080×1920clear of app ui
  8. contrast15 / 15wcag pass
  9. golden frames0.99 ssimno drift

launch day is one day.
releases are every week.

Tag a release, get a video

It reads your release notes, or the commits since the last tag, and renders with the real numbers. A GitHub Action attaches the file to the release itself.

git tag v1.2.0 && git push --tags

  → release.mp4 attached
     4 commits · 80 files changed
     "npm i yourpkg@1.2.0"

Open a PR, see the difference

It works out which pages the PR touches, captures them on production and on the preview, scores the change and comments once, then edits that comment on every new deploy instead of stacking up new ones.

shipreel preview

  page      result      ssim
  /         changed     0.911
  /about    unchanged   0.999

one plan, every shape.

Five frame sizes (1920×1080, 1080×1920, 1080×1080, 1080×1350, 1000×1500) and twenty-six presets that each carry their platform's safe zone, caption style, duration window and size budget, taken from that platform's own documentation.

TikTok, Instagram Reels and Stories and feed, YouTube and Shorts, X, LinkedIn, Facebook and Facebook Reels, Threads, Bluesky, Mastodon, Reddit, Snapchat Spotlight, Pinterest, WhatsApp status, Telegram, Slack, Discord, Vimeo, dev.to, GitHub README, Product Hunt, App Store and Google Play previews.

what you get.

In the box

  • The /shipreel skill, for Claude Code, Codex, opencode, Cursor, or any agent that reads skills
  • The standalone CLI, when you'd rather not involve an agent
  • 26 platform presets across 5 frame sizes
  • Scene kits: terminal, code editor, phone frame, browser frame, API card, cursor, game HUD
  • Release-video and PR-preview GitHub Actions
  • Launch kit: covers, thumbnails, an X thread, a LinkedIn post, embed snippets, credits
  • Launch images in your own palette and fonts: link preview, X, GitHub social preview, Product Hunt gallery, LinkedIn carousel, each one checked
  • Launch copy checked against each platform's limits before you post it
  • Captions, cutdowns, stories, carousels, and nine-language localisation
  • Music and sound effects cleared for commercial use
  • Updates with one command, for as long as it is maintained

What it needs

  • Node.js 22 or newer
  • FFmpeg on your PATH
  • Chrome, for capturing your real interface
  • An agent, only for the bespoke path; the CLI works alone

Rendering runs on your machine. No account, no upload, no per-render fee, and nothing posted anywhere. shipreel writes files and stops.

free · open source · MIT

one line.
every feed.

Install it once. Every video it makes leaves ready for 26 platforms, checked before it goes out.

$ npx @irvinosazee/shipreel skill install

Puts the skill in ~/.claude/skills. Restart Claude Code and say let's /shipreel.

  • 26platform presets across 5 frame sizes
  • 297tests on every push
  • $0MIT. Unlimited videos, yours commercially, no watermark
  • 3kinds of video: launch, release, pull-request preview
★ star on github the whole price

Every route, including Codex and opencode, is in the README; the manual covers every flag. To see what I build next, follow me on GitHub or LinkedIn.

shipreel --help

straight answers.

There's a free tool called /brag. How is this different?

shipreel is a fork of /brag by Shunit Haviv Hakimi, and that project is good: if it does what you need, use it. Both are free; the difference is what sits on top. /brag is a prompt and a set of assets telling an agent how to make one landscape video. shipreel verifies what comes out, reflows one plan across five frame sizes and 26 platforms, captures your running interface, cites on-screen claims to files in your repo, and adds launch images, release videos, PR previews, a GitHub Action and a standalone CLI. One script and no tests became 40 scripts and 297.

Does my code leave my machine?

No. It reads your repo and renders locally; there is no shipreel server and no account. shipreel itself sends nothing. Be aware that the tools it drives have their own behaviour: Hyperframes is fetched from npm to render and reports anonymous usage of its own, and live-metrics mode calls GitHub or npm because you asked it to.

Can I use the videos commercially?

Yes. No royalty, no watermark, no credit to shipreel required. The bundled music is CC BY 4.0 by Sascha Ende, so credit him if you use it; every launch kit writes that line into credits.txt for you. Sound effects are CC0 by Kenney. Don't register a render that contains the music with YouTube Content ID; that licence forbids it.

Why is it free?

Because a tool that reads your private repository should be one you can read too, and because I would rather a lot of people use it than a few pay for it. It is MIT: use it, fork it, ship it inside your own product. If it saves you an evening, a star on GitHub is the whole price.

What if it breaks?

It drives Hyperframes, FFmpeg and Chrome, which move independently of it, so it can. A nightly job renders a real composition against the current Hyperframes, so breakage shows up within a day rather than when you need a video. If it's broken for you, open an issue, or send the fix, it's open source.

Do I need Claude Code?

No. The CLI reads your package metadata, README and git history, captures your site, and fills a clean template with no agent at all. An agent writes something made for your project instead of a filled-in template, which is better, but it isn't required.

How do I hear about new versions?

On GitHub, Watch → Custom → Releases on the repo and you get one notification per release, video included. To follow what I build next: GitHub, LinkedIn, or Medium.