Features

six reviewers’ worth of attention on every pull request.

Every capability below exists for one reason: so you open a pull request, hear what could break, fix it fast and merge with momentum. Here is exactly what Rubberduckly does once it joins your thread.

See plans

comments that explain the why

A bare “possible null” is noise. Rubberduckly names the line, shows what breaks, and says why, so you fix the cause instead of silencing the warning. Reply in the thread and it answers with the context you were missing.

Teammates stop translating linter output for juniors. The explanation is already there.

In your flowPosts within minutes of opening the pull request, as a normal review thread on GitHub or GitLab.

#2181 Cart: handle cleared state · Conversation

Rubberducklyon src/cart/summary.ts:27 · 4 min ago

parseCart() now returns null for an empty cart, but CartSummary still reads .items.length. That throws on checkout the moment a shopper removes their last item.

Priya N.2 min ago

Does guest checkout hit the same path?

Rubberducklyjust now

Yes. GuestCart shares the helper, so both flows break. Returning { items: [] } fixes both in two lines.

Rubberduckly is drafting the fix

Thread synced 2m ago · 1 unresolved

rules in the words you’d use out loud

Write “amounts are integer cents, never floats” and it is enforced on every pull request that touches billing. Prefer config? Put the same rule in YAML and scope it by path.

Choose per rule whether a finding blocks the merge or just nudges. House style gets written once, not repeated in every thread.

In your flowRules live in the dashboard or in a file in your repo, versioned alongside the code they guard.

Kestrel Works · Review rules

Plain EnglishYAMLHistory

New rule · applies to billing/**Never compare money with floats; amounts are integer cents.

Add rule⌘↵ to save

Billing changes need a testBlocks merge · billing/**

Amounts are integer centsBlocks merge · billing/** · added just now

TODOs carry a ticket idNudge · all files

Prefer early returnsOff · web/**

Saved · applies to 6 repositories

risk scores that point at the scary diffs

Each pull request gets a score out of 100 based on what it touches: fragile modules, high-traffic paths, files that churn weekly. Open the 82 first, breeze past the 3.

Reviewer time goes where a mistake would cost the most.

In your flowThe score lands on the pull request title. Select several and request a second reviewer or hold the merge in one move.

Kestrel Works · Risk map · Nov 1, 2026

Pull request	Risk	Author	Touches	Status
#2184 Retry failed card captures	82	Tomasz K.	billing/capture.ts	Needs review
#2175 Rotate webhook signing secret	71	Callum B.	auth/webhooks.ts	Needs review
#2181 Cart: handle cleared state	64	Aisha R.	cart/summary.ts	Changes requested
#2177 Cache shipping rates for 5 min	47	Dev M.	shipping/rates.ts	Approved
#2179 Bump logger to 4.2	12	Callum B.	package.json	Approved
#2172 Fix onboarding copy typo	3	Aisha R.	web/copy.ts	Merged

2 selectedRequest second reviewerHold mergeSynced 2m ago

1–6 of 23 openPrev · Next

fixes you commit with one click

Spot the problem, press enter. The suggested change lands on the branch as a clean commit and CI is already running before you close the tab. No round trip for a one-line change.

Batch several suggestions into a single commit when you want a tidy history.

In your flowCommits go to the pull request branch under your name, so blame and history stay honest.

#2181 · src/cart/summary.ts · Suggested change

Rubberducklysuggested a change on line 27

27- const count = cart.items.length;

27+ const count = cart?.items?.length ?? 0;

Commit to fix/cart-clearedDismiss

Committed 7be1d04 · checks running

review analytics that show where time goes

Cycle time, time-to-first-comment and reviewer load on one page. Find the pull requests that wait for days and the teammate quietly carrying every review.

Your retro stops running on feelings and starts running on a chart.

In your flowFilter by repository, team or week, then bring the page to your Monday planning.

Kestrel Works · Analytics · Oct 3 – Nov 1, 2026

Median time to merge6.4 h
−18.2% vs Sep

First comment3 min
−41.0%

Pull requests merged412
+12.4%

Oct 22 · 8.9 h
peak: release week

Updated · Synced 2m ago

a command bar for people who hate hunting

Press ⌘K, type a few characters, and land on the pull request, the rule or the repository you meant. Keyboard shortcuts cover approve, hold and batch.

Triage a full queue without touching the mouse.

In your flowWorks from the dashboard and across every connected repository in the workspace.

Kestrel Works

captureesc

Pull requests

#2184 Retry failed card captures82↵

#2151 Void uncaptured authorisations↓

Rules

Billing changes need a test

Actions

Hold merge on selectedH

3 results · Synced 2m ago

Security and reliability

your code is read to review it, then left alone

read access you can scope
Grant access to the repositories you pick, nothing else. Revoke it from GitHub or GitLab at any moment.
sso and audit logs
The Migration plan adds SSO and SAML sign-in, plus audit logs of every rule change and committed suggestion.
self-hosted runner option
Keep diffs inside your own network by running the review engine on your infrastructure.
reviews that keep arriving
If a review fails to post, it retries on its own and tells you in the pull request instead of going silent.

Integrations

it sits where your team already works

Connect once and risk flags and review summaries show up in the tools you have open all day.

ToolWhat it doesPlan

GitHub

Reviews every pull request and commits suggestions to the branch.

All plans

GitLab

Reviews merge requests with the same comments, rules and scores.

All plans

Slack

Posts high-risk pull requests to the channel you choose.

Flock, Migration

Jira

Checks TODOs against ticket ids and links findings to the issue.

Flock, Migration

Zapier

Sends review events anywhere else you need them.

Flock, Migration

Your next pull request

pick a plan and merge with the answers already in the thread.

One payment per plan. Connect GitHub or GitLab and let the next pull request start with the explanation.

See plans