Pullmaster

A GitHub App for your team

Who should review this PR?

Pullmaster analyzes code ownership, expertise, and workload across your team β€” then suggests the best reviewer for every pull request.

Install on GitHub

Free to install. No credit card required.

pullmasterai bot commented 2 minutes ago

Suggested Reviewers

@sarahchen — Has recent commits touching src/auth/ and reviewed 3 pull requests modifying the OAuth module in the last 30 days.

Code reviews shouldn't feel like this

Reviewer assignment is broken. Sound familiar?

  • "@here who can review this?" on repeat in Slack
  • The same 2-3 people review everything
  • Round-robin ignores who actually knows the code
  • PRs sit for days waiting on the wrong reviewer
  • New contributors get no guidance on who to request

Getting started

Most teams are live in under 5 minutes

1

Install the GitHub App

One click to add Pullmaster to your repositories. No configuration needed.

2

Open a Pull Request

Pullmaster figures out who knows this code best and who has bandwidth to review it.

3

Get the Best Reviewer

Pullmaster suggests a reviewer with an explanation, or assigns them directly with a GitHub review request. You choose.

One install, five ways to ship better reviews

Pullmaster is more than reviewer picks β€” governance, ownership, and IDE intelligence ship with the same GitHub App.

🎯

Core product

Smart reviewer recommendations

Pullmaster ranks every eligible teammate using real repo history, then explains who should review β€” on demand in your PR.

  • @pullmasterai suggest for recommendations with reasoning
  • @pullmasterai assign to request the top reviewer on GitHub
  • Risk-aware matching for routine vs critical changes
  • Clear explanations tied to your changed files
πŸ”„

Keep PRs moving

Reviewer escalation

When a requested reviewer goes quiet, Pullmaster automatically requests the next-best match so reviews do not stall.

  • Configurable timeout and max escalations per PR
  • Respects real review activity before escalating
  • Runs on a schedule so you do not babysit PRs
πŸ›‘οΈ

See where knowledge lives

Governance & ownership health

Pullmaster maps your repo into code areas, surfaces bus-factor risk, and recommends who should own each part of the codebase.

  • Ownership health score and per-area risk badges
  • Bus factor, concentration, and knowledge-gap insights
  • Actionable backup-owner recommendations
πŸ“‹

Ownership without auto-nagging

PULLMASTER & CODEOWNERS preview

Use a CODEOWNERS-compatible PULLMASTER file for path ownership signals without triggering GitHub’s automatic review requests.

  • Same format as CODEOWNERS β€” drop in root, .github/, or docs/
  • One-click preview of a generated CODEOWNERS from real activity
  • Ownership rules inform matching, not noisy auto-assigns
πŸ”Œ

Intelligence in your IDE

MCP repo intelligence

Connect Pullmaster to Cursor, Claude Desktop, or other MCP clients for read-only repo intelligence where you already work.

  • Ownership metrics, code areas, and reviewer profiles
  • Live PR reviewer candidates and file familiarity lookups
  • OAuth 2.1 β€” secure, scoped access from your dashboard

The signals behind every match

Every recommendation blends six scoring signals from your repo history β€” not who's next in line.

πŸ“

Recent file history

Finds who recently worked on the files in your PR β€” not who touched them two years ago

πŸ‘€

CODEOWNERS-aware

Respects your existing CODEOWNERS rules and designated maintainers

🀝

Reviewer history

Knows which reviewers give the best feedback on each teammate's code

🧠

Beyond file paths

Finds reviewers who understand the concepts in your code, even if they haven't touched the exact files

βš–οΈ

Workload balancing

Spreads reviews across your team so the same two people don't review everything

🎯

Risk-aware routing

High-risk PRs go to your most experienced reviewers. Routine changes get spread around.

πŸ”„

Auto-escalation

If a reviewer doesn't respond in time, Pullmaster automatically requests the next best candidate so PRs never go stale

Why not just CODEOWNERS?

CODEOWNERS solves a different problem. Here's what it can't do.

CODEOWNERS problems

  • Static file β€” must be manually updated when ownership changes
  • Path-based only β€” maps directories to teams, not reviewers to code
  • Goes stale as teams and codebases evolve
  • No workload awareness β€” cannot route based on capacity or availability
  • Binary ownership β€” you're an owner or you're not, no scoring or ranking

Pullmaster advantages

  • Dynamic β€” learns from every merged PR
  • Matches reviewers by real contribution history, not just file paths
  • Always current β€” no file to maintain
  • Balances workload across the team automatically
  • Scores reviewers on a spectrum of expertise

Want path ownership scoring without GitHub's automatic reviewer requests? Rename your CODEOWNERS file to PULLMASTER β€” Pullmaster reads it with the same syntax.

Frequently asked questions

Ready to improve your code reviews?

Install Pullmaster on your GitHub repositories and start getting better reviewer recommendations today.

Install on GitHub

Free to install. No credit card required.

Questions? Reach out at hello@pullmaster.ai or book a call .