Turn your pull requests
into videos.

Get a short narrated video that explains your pull request.

Paste any GitHub PR URL below

Used by teams at

Chatgrid
Gambit Markets
Dreamwell
Market Terminal
Breakouts & Setups
Chatgrid
Gambit Markets
Dreamwell
Market Terminal
Breakouts & Setups
Chatgrid
Gambit Markets
Dreamwell
Market Terminal
Breakouts & Setups

The pullstory difference

Same PR. Completely different experience.

BeforeThe GitHub PR view
github.com/acme/api/pull/847
23 files changed+1,247 −389
src/auth/oauth.ts+47 −3
src/auth/session.ts+12 −19
src/api/user.ts+8 −4
src/db/migrations/0042_session.sql+56 −0
lib/jwt-helpers.ts+89 −12
middleware/rate-limit.ts+34 −7
src/auth/providers/google.ts+62 −0
src/auth/providers/github.ts+58 −0
+ 15 more files…
− export function login(email, pw) {
− const token = jwt.sign(...)
+ export async function login(email, pw) {
+ const token = await jwt.signAsync(...)
+ if (!token) throw new AuthError(...)

Wall of diffs. Where’s the story?

23 files. 1,247 lines. Reviewers click through diffs trying to reverse-engineer the why. The intent is buried in the changes.

AfterThe pullstory view

A narrated walkthrough. Instant clarity.

An AI-narrated story with diagrams that show what changed, why it matters, and how it fits the rest of the system. 3 minutes. No detective work.

Everything you need

Built for devs drowning in AI-generated code.

Narrated stories

AI narration that actually walks you through it.

Every pull story is a 2-to-5-minute video with AI voiceover that explains what changed and why. Word-level transcript. Scrubbable timeline. Watch the next PR from bed.

Try it free
2
The new auth flow
1:24 / 3:07
Architecture diagram generated by pull/story showing Browser → API Handler → Auth Service → Google OAuth, with Auth Service writing to the Sessions database.
› “The API layer now verifies the token asynchronously before hitting the database…”

Adaptive diagrams

Diagrams that change shape per step.

Architecture for the overview. Sequence for the auth flow. ER for the new tables. Flowchart for the branching logic. pull/story picks the right diagram type for each step — automatically.

Try it free
Architecture
Sequence
ER
Flowchart

Key points

Straight to the parts you actually care about.

Every pull story surfaces the risky bits: DB migrations, new env vars, external API calls, auth changes. Stop hunting for the 3 lines that matter inside a 1,200-line PR.

Try it free
pull/story found
4 things worth your attention
Database migration
Adds a NOT NULL column to the sessions table.
New environment variable
JWT_SIGNING_KEY must be set before boot.
Auth behavior change
Login handler is now async — callers need updating.
New external API call
Adds outbound dependency on Google OAuth.

GitHub-native

Posted right inside your PR. Zero context-switching.

pull/story is a GitHub App. Open a PR — about 60 seconds later, a thumbnail, risk summary, and step diagrams appear right in the PR description. No new dashboard to learn.

Try it free
acme / api· pull/847
Open
feat: async token verification + Google OAuth
moshi wants to merge 23 commits into main
pull-storybotcommented 1 min ago
GitHub App
I generated a story for this PR — 6 steps, 3:07.
pull/story3:07
Auto-generated by the pull/story GitHub App — no dashboard to open

A note from the founder

pull/story exists because of an
11:32 PM text message.

Hey — I'm Moujtabah Karim. Friends call me Moshi; on GitHub I'm EchoMosh.

I wasn't planning to build a PR tool. I was texting my buddy Anthony Bobsin → and he said the line.

“big pain point for me right now is reviewing all the code that we’re generating”

11:32 PM. It clicked in about thirty seconds. Everyone ships 3× more code than last year, nobody writes PR descriptions, nobody reads the diffs, everybody just merges.

So I built pull/story. Not another nitpicky AI reviewer — an AI-narrated story of your PR. DM me on GitHub if you try it. I read every message.

M
Text message from Anthony Bobsin: 'big pain point for me right now is reviewing all the code that we're generating'
The actual message. 11:32 PM. The spark.

Pricing

Both are free.
One of them has a video.

Pick your plan.

Do it yourself

The Hard Way

The way you review pull requests now.

$0/ forever

What you get

  • A raw pull request diff
  • Thousands of lines of code
  • A scroll bar
  • An “Approve” button
  • Your best guess
You're already on this plan
The obvious one

pull/story

The Easy Way

Paste a link. Get a narrated video. That's it.

$0/ 10 min of video per month

Need more? Pro is $19/mo for 120 min of video.

Everything above, plus

  • Narrated video walkthrough of every PR
  • Auto-generated diagrams of your architecture
  • Code highlights synced to the voiceover
  • One-click share with your team
  • A direct line to the founder
Sign up free with GitHub →

No credit card for free · Upgrade only when you need more

Questions?

A few things people ask.

  • Is it really free?

    Yes. 10 minutes of narrated video per month on the free plan — no credit card, no catch. A short PR is around a minute of video, so most devs never hit the limit. Pro kicks in only when you actually need more.

  • How does the pricing work?

    Pull/story is metered by video length, not PR count. Free gives you 10 minutes of video per month. Pro is $19/month for 120 minutes and includes unlimited AI chat + diagrams on top of the video. A 1,000-line PR is usually 2-3 minutes.

  • Can I use Claude to make pull stories?

    Soon. We're building a Claude MCP — and pull stories won't just be for PRs. You'll be able to ask Claude to visualize any part of your codebase: a single feature, a file, the whole auth system. Right from your editor.

  • What happens when I run out of minutes?

    You keep access to everything you've already generated and can still chat with the AI — you just can't generate new pull stories until the next cycle, or upgrade to Pro for 120 min/month.

  • How do I give feedback?

    DM @echomosh_ on X (fastest), ping @EchoMosh on GitHub, or email moshikarim@proton.me. I read every single message.