For engineers who hate self-promotion

You shipped it.
Now go say so.

MergeDraft turns your merged PRs into demo notes, status updates, 1:1 talking points, and perf-review bullets — in your voice, with the impact actually surfaced.

Connect GitHub — freeSee how it works
No credit card·Read-only GitHub scope·Your code never leaves the diff summary
github.com / acme / checkoutinput · 4 PRs
Refactor cart reducer to handle multi-currency
#1842·feat/multi-currency·merged 2d ago
+412−218
Fix race condition in checkout polling loop
#1839·fix/poll-race·merged 2d ago
+38−24
Add Stripe Tax integration
#1828·feat/stripe-tax·merged 2d ago
+506−92
Bump axios + audit migration
#1820·chore/axios·merged 2d ago
+14−19
translate
Sprint demo · for product reviewoutput

Checkout — Sprint 23 highlights

→
Unblocked international launch by introducing multi-currency support across the cart pipeline. 4 currencies live in staging.1842 · refactor cart reducer to handle multi-currency
→
Eliminated checkout flicker reported by 2 enterprise customers by fixing a race condition in the polling loop. 0 incidents since deploy.1839 · fix race condition in checkout polling loop
→
Removed manual tax workflow by integrating Stripe Tax — ~6 hrs / week back to the finance team.1828 · add Stripe Tax integration
generated · haiku-4-5 · 1.4s
Built by & for engineers atStripeLinearVercelShopifyGitHubNotion
The translation gap

You speak diff. They speak outcome.

The same week of work, told two different ways. The right column is the one that gets you a promotion.

What you wrote
$fix(checkout): debounce poll, drop dupe events
$refactor: extract CurrencyProvider, hoist FX cache
$chore: bump axios, fix CVE-2024-39338
$perf(orders): paginate & lazy-load line items
What they need to hear
01Resolved a checkout flicker affecting two enterprise customers — zero incidents since.
02Unblocked international launch by enabling multi-currency carts.
03Closed a high-severity vulnerability ahead of the SOC 2 audit window.
04Cut order-page load time from 1.8s to 380ms — measurable for ops dashboards.
Output formats

One sprint of work. Four audiences.

Same source PRs, different translations. Pick a template; tweak the tone; copy & paste where it needs to go.

Sprint demo

audience: PMs · cross-functional partners

This sprint we shipped multi-currency checkout. What that means:

  • Carts now hold non-USD line items end-to-end (4 currencies live in staging).
  • Checkout flicker reported by Acme & Brightline is fixed — 0 repeat tickets.
  • Stripe Tax replaced our manual workflow; saves finance ~6 hrs/wk.
~120 words·3 bullets + tldr

1:1 update

audience: your manager

Quick wins from this week — flagging in case useful for staffing/roadmap:

  • Multi-currency cart is in staging. I think we can demo it next Tuesday.
  • Race condition under checkout polling is fixed. Want me to write up a postmortem?
  • Heads up: the axios bump touched 14 files. Worth a heavier review.
~80 words·conversational

Performance review

audience: skip-level · calibration committee

Impact > Scope of work

  • Drove international expansion readiness. Authored multi-currency cart refactor (#1842). Unblocked a previously stalled $1.2M ARR initiative.
  • Improved customer reliability. Diagnosed and fixed a race condition (#1839) that produced 12 customer reports across Q3.
STAR format·quantified · linked

Brag doc entry

audience: future-you

Sprint 23 · Apr 14 – Apr 28

  • Shipped multi-currency carts. Owner. ~620 LOC across 8 files.
  • Fixed checkout race condition. Pulled traces, repro'd locally, landed fix in 2 days.
  • Integrated Stripe Tax — replaced 3-step manual workflow.
  • Closed CVE-2024-39338 ahead of SOC 2 window.
archive·append-only
How it works

Three steps. About 90 seconds.

step 01

Connect GitHub

Read-only OAuth. We pull PRs you authored — never source code beyond what's already in the diff summary.

$ mergedraft auth login
→ opening github.com/login/oauth…
✓ connected as @you
✓ 14 repos · 47 PRs in last 90d
step 02

Pick a window & format

Last week. Last sprint. A custom range. Then choose what you're writing — demo, 1:1, perf review, or your own template.

range = last sprint (Apr 14 – Apr 28)
prs = 8 selected
format = sprint-demo
tone = concise
step 03

Edit, copy, send

The draft is yours — edit inline, regenerate sections, swap tone. One click to clipboard or markdown export.

✓ draft generated · 1.4s
✓ 3 bullets · 118 words
→ copy to clipboard
→ save to history
Field reports

From people who hate marketing copy.

I used to dread the Friday update Slack. Now I paste in a date range, edit two bullets, and ship it. My manager actually replied this week.
PK
Priya K.staff engineer · fintech
Wrote my whole self-eval in 40 minutes. Last cycle it took me a weekend and I still undersold the migration work. Promoted this round.
DM
Devon M.senior swe → staff · marketplace
The output isn't magical, it's just correct. It links the right PRs, doesn't invent numbers, and stops at the right level of detail. That's all I wanted.
RC
Ravi C.tech lead · infra
Pricing

Free to try. $12 to make it a habit.

Cancel any time. Annual is 20% off. Student? Open-source maintainer? Email us — it's on the house.

Free
$0/ forever

Enough to write a sprint demo every two weeks.

  • 5 generations / month
  • All 4 output formats
  • Last 30 days of PR history
  • Public & private repos
  • History & brag doc archive
  • Tone customization
Start free
Pro
$12/ month

For the engineer with a perf review on the calendar.

  • Unlimited generations
  • All formats + custom templates
  • Full PR history (no time limit)
  • Brag doc — rolling personal archive
  • Tone customization (concise / formal / casual)
  • Priority model · faster generations
Start 14-day trial
FAQ

Reasonable questions, honestly answered.

Does my source code get sent to an LLM?+

No. We send PR titles, descriptions, file names, and the diff summary (the +N/−M line counts and patch hunks GitHub already shows you). The actual file contents stay on GitHub.

What GitHub scope does it ask for?+

Read-only access to PRs you authored. We don't ask for write access, and we don't store your repo contents.

What about Jira / Linear / GitLab?+

On the roadmap. GitHub-only at launch — we'd rather do one thing well. Linear and Jira are next; GitLab after that.

Will it sound like marketing slop?+

That's the bar we're trying to clear. The default tone is “engineer-talking-to-engineer.” Tweak it down to “concise” or up to “exec-formal” if your audience needs it.

Can I use this for interview prep?+

Yes — STAR-format bullets are baked into the perf-review template, and full interview-story generation is on the v2 roadmap.

Is there a team plan?+

Soon. Manager views with consolidated team impact are the v2 focus. Drop your email below if you want to be a beta team.

Stop letting your work speak for itself.
It's bad at it.

Connect GitHub. Pick a sprint. See your work in a language your manager understands.

Connect GitHub — freeSee pricing