Skip to main content

After the review, share what shipped

Yanib connects code changes to release communication. Prepare the update, review what should be public, and deliver it through the workflows you configure.

Set up release communicationA real public release storyA real shipping profile

Release stories, surface follow-up, profiles, embeds, and agent tools remain separate capabilities. PR review does not automatically enable docs changes, downstream issues, or public broadcasting. Each workflow keeps its own configuration and permissions.

You ship Yanib broadcasts

Yanib drafts updates from your commits and PRs. Review the draft and its evidence, then share it through the channels you configure. Choose approval or an enabled automatic workflow, with formatting and routing for each destination.

One prepared update

  • From your commits and PRs
  • Draft and evidence review
  • Approve or run autopilot
Publish everywhere
GitHub ReleasesNative release entryPublic story pageHosted page, your brandSlackTeam channelsDiscordCommunity serversEmail subscribersVerified list, one clickRSS feedEvery feed readerEmbeddable widgetInside your productPublic APIJSON, no auth

Plus one more audience that never reads announcement posts. Meet the ninth channel: agents.

Everything you need to ship in public

Detect, write, publish, and build a public record of what you ship.

01 · Detect

Catch new capabilities where they enter the codebase

  • Structural surface detection

    Check configured paths for added files, schema additions, or custom pattern matches. Each match keeps its diff evidence and enters review as a candidate.

  • A persistent capability ledger

    See what Yanib found, the commit or merged PR behind it, whether it was announced, and which declared docs stayed unchanged.

  • Docs follow-up with consent

    Declare related docs in .yanib.yml. Yanib records stale docs and, when repo write access is enabled separately, opens a reviewable update PR.

02 · Write

Release notes that write and review themselves

  • AI drafts from your real PRs

    Draft release notes from connected commits and PRs using your configured triggers. Release review can flag missing entries, overclaims, and breaking changes for you to check before publishing.

  • Rewrite in your voice

    Concise, detailed, user facing, or technical, plus multi audience versions for devs, PMs, and end users.

  • Translate for every reader

    Localize entries for international readers with one click. Translations are cached per release.

03 · Publish

One publish. Every channel your users live in

  • Everywhere at once

    Publish to the channels you configure. Enable automatic publishing separately when that workflow fits your repository.

    Publish releaseon tag push · autopilot
    • GitHub Releases✓
    • Slack✓
    • Discord✓
    • Email subscribers✓
    • Public story page✓
    • RSS✓
    • Widgets✓
    • API✓

  • Team digests

    AI velocity reports on your cadence, daily, weekly, or monthly, delivered to Slack with per contributor breakdowns.

  • Import your history

    One click backfill turns your past tags into structured releases, so your story page starts with history, not a blank page.

04 · Be known

What you ship becomes who you are

  • Your public shipping profile

    Public releases build a record of what you’ve shipped. This card is the real product output, generated from published public releases.

    Live shipping card for binaydhakal, updated on every release

    live, updates on every release

    View the profile

  • README cards & badges

    SVG profile cards and per repo release badges for any GitHub README. They update automatically on every ship.

  • Year in review + streaks

    A shareable annual recap, plus week based ship streaks rendered right on your card.

One embed, drop it anywhere

Add the script once, pick a component, paste the tag. Works anywhere you can drop HTML.

Preview

Stories

acme/web

v2.4.0Team roles & SSO
v2.3.2API rate limits
v2.3.0Dark mode

Copy

Embed markup for Story feed

<script src="https://yanib.dev/sdk.js"></script>
<yanib-stories
  repo="owner/repo"
  theme="light"
  limit="5">
</yanib-stories>

Use repo="owner/name" instead of slug when it fits your setup.

Components

Pick a component to update the preview and the copy and paste snippet.

Live playground: Embed demo

Looking for agent tools? Explore Yanib for agents

Connect declared surfaces to follow-up

Surface detection helps route confirmed changes to the documentation and audiences you configure. Keep the source review and the post-merge communication decision connected without treating every code edit as a public announcement.

Read the surface detection guide