Keep your docs fresh automatically, generate release notes from real commits, and produce release videos with Remotion + browser-automation captures. No-op silently on quiet days.

Keep your docs fresh automatically. Generate release notes from real commits. Produce release videos with Remotion + browser-automation captures, on the cadence you choose.

What it does

Daily — checks if anything actually shipped in the last 24h. If yes: update the docs site, CHANGELOG, "last updated" timestamps, cut a GitHub release if the version lacks one. If nothing shipped, no-op.
Weekly — produce release-notes MDX (docs site) and a release-notes blog post (marketing site) from real commit history, with significance evaluation so trivial commits don't headline.
On-demand — generate release videos: Remotion renders the polish (titles, transitions, music bed, brand colors); qa-use / browser-use captures the real product flow.

Agents

Coder (ours is Picateclas) — docs PRs, MDX writes, CHANGELOG bumps, release tagging.
Forward-Deployed Engineer (ours is Jackknife) — qa-use captures and browser-automation for release-video recording.
Content Writer — release-notes blog post drafting (separate from the in-repo CHANGELOG).

Tools & Skills

Built-in (ships with agent-swarm)

agent-fs (video drafts, intermediate compositions, audio assets), gh / glab CLI (PRs, releases, tags), slack-post (release-shipped notifications).

Custom (swarm-managed)

video-generation — Remotion is the default stack (project layout, brand fonts/colors, default music bed, render pipeline, "honest read" pacing all encoded).
browser-use-cloud — escape hatch when datacenter IPs get blocked (YouTube transcripts past bot walls, captcha pages, login walls). Drives a real cloud browser via Browser Use Cloud.

Third-party providers (popular tools we use)

Remotion — programmatic video framework. Default stack for release videos.
qa-use — agent-first browser-automation CLI. Drives a real browser through your product so captures are real, not mockups.
browser-use — alternative browser-automation framework (also available via Browser Use Cloud).
Fumadocs — MDX-based, Next.js docs site. This site you're reading is built on it.

Workflows / Schedules

daily-docs-update — daily. Checks if any PRs merged in the last 24h. No-op if none. Otherwise updates docs + CHANGELOG + timestamps, cuts a release if needed. See the No-op pattern.
docs-site-releases — weekly. Generates MDX release notes for the docs site: pulls commits, evaluates significance, plans, writes MDX, validates, opens a PR.
weekly-new-releases — weekly. Release-notes blog post for the marketing site (product repos only, not internal infra).

Patterns used

No-op When Nothing Changed — the daily docs job skips silently on a quiet day.

Tips for new swarm users

"No-op when nothing changed" is the most important property. Agents that always write something fill your changelog with noise. Detect "did anything ship?" and skip if not.
Pair Remotion + qa-use for release videos. qa-use captures the real flow (so the demo isn't a lie); Remotion adds polish. Don't do both in one tool.
Cap video length — 45–90 seconds, hard limit. The skill's "honest read" pacing enforces this.
browser-use-cloud is your escape hatch when datacenter IPs get blocked. Don't fight Cloudflare from your swarm; drive a real cloud browser.
Two-track release docs — in-repo CHANGELOG.md (developer-facing, terse, all changes) vs. marketing release notes (customer-facing, narrative, only what users care about). One audience, one format.
Significance-evaluate commits before writing — a patch dependency bump shouldn't headline a release.

Self-Documenting & Release Reports