Code ownership intelligence

Code ownership intelligence for GitHub teams

Pullmaster learns from your GitHub history to show who knows each part of your codebase, where knowledge is concentrated, and who should review every pull request.

Get reviewer recommendations, ownership health, bus-factor insights, and MCP-powered repo intelligence from one GitHub App.

Install on GitHub See example output

Free during early access. Works with private repos. No raw source code stored.

Code reviews break when ownership is invisible

As teams grow, code ownership becomes tribal knowledge. The same senior engineers get pulled into every review, new developers do not know who to ask, and critical systems quietly become owned by one person.

The same 2–3 engineers review everything.
New developers do not know who to request.
CODEOWNERS gets stale.
Critical code has no backup owner.
PRs sit because the wrong reviewer was picked.
Managers cannot see knowledge concentration until someone leaves.

Product

PULLMASTER turns GitHub activity into ownership intelligence

🎯

Reviewer recommendations

Get ranked reviewer suggestions for every pull request, with explanations based on file familiarity, recent changes, review history, and workload.

🗺️

Ownership map

See who owns each area of the codebase, who the backup owners are, and where ownership is unclear.

⚠️

Bus-factor risk

Find code areas where knowledge is concentrated in one person or where no clear owner exists.

⚖️

Workload-aware routing

Avoid sending every review to the same senior engineers by factoring in current review load.

📋

CODEOWNERS-compatible rules

Use a PULLMASTER file with CODEOWNERS-style syntax to guide ownership without triggering GitHub's automatic reviewer requests.

🔌

MCP repo intelligence

Ask Cursor, Claude Desktop, or any MCP client questions about ownership, reviewer candidates, risky areas, and file familiarity.

Reviewer suggestions your team can trust

pullmasterai bot commented just now

Suggested Reviewers

@sarahchen — Recently committed to app/auth/session.rb and reviewed 8 PRs touching the auth module in the last 90 days.

Mention @pullmasterai to provide feedback.

Every recommendation includes a short, specific explanation tied to the files in your PR. Request someone else if you disagree — Pullmaster only acts when you ask.

See where your team has knowledge risk

Beyond individual pull requests, Pullmaster gives engineering teams a repo-level view of code ownership health.

Code areas

acme-corp / platform-api

Ownership health 72

Critical (bf 0)

Bus factor 1

Unowned

Healthy (bf ≥ 2)

68 %

Most concentrated

@mikelee (3)

Billing

One primary owner and no backup.

Auth

High review concentration around two engineers.

Frontend checkout

Unclear ownership after recent team changes.

API clients

Healthy, with three active contributors.

MCP repo intelligence

Cursor · MCP

User:

Who knows the billing system?

PULLMASTER:

The strongest owner is @jane based on 42 commits, 16 reviews, and recent changes across app/models/billing and app/services/invoicing.

Backup candidates:

@mark — reviewed recent invoice changes.
@sarah — owns adjacent payments code.

Risk: Billing has high ownership concentration. Add a backup owner.

CODEOWNERS is static. PULLMASTER is behavioral.

CODEOWNERS	PULLMASTER
Static file	Learns from GitHub activity
Path-based	Path + review history + file familiarity
No workload awareness	Factors in reviewer workload
Binary ownership	Scores expertise on a spectrum
Can go stale	Updates as the team works
Automatically requests reviewers	Can suggest, assign, or just power the dashboard

Pullmaster does not need to read your CODEOWNERS file. Instead, you can add a PULLMASTER file using familiar CODEOWNERS-style syntax to guide ownership rules without causing GitHub to automatically request reviewers.

One GitHub App. Three ways to understand your codebase.

Route reviews, map ownership, and query repo intelligence — all from the same install.

Route reviews

🎯

Core product

Smart reviewer recommendations

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

Mention @pullmasterai right in a PR to get recommendations or request a reviewer
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

⚖️

Spread reviews fairly

Workload-aware matching

Pullmaster factors in current review load so the same senior engineers are not assigned every PR.

De-prioritizes reviewers with pending change-request reviews
Spreads routine reviews across the team
Still routes critical changes to your most experienced reviewers

Understand ownership

🛡️

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 file support

Use CODEOWNERS-style rules in a PULLMASTER file to boost designated owners without triggering GitHub's automatic reviewer requests.

Same format as CODEOWNERS — drop in root, .github/, or docs/
Boosts reviewers who own the changed files
Rename CODEOWNERS to stop GitHub auto-requests

🔍

Ownership from real activity

Generated ownership rules preview

Pullmaster can generate a CODEOWNERS-style preview from real contribution history, code areas, and file familiarity. Copy it into CODEOWNERS or PULLMASTER when you are ready.

Built from real code areas and file familiarity
Up to three owners per area, plus backups
Preview only — copy it when you are ready

Bring intelligence into your tools

🔌

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 expertise
Live PR reviewer candidates and file familiarity lookups
OAuth 2.0 with PKCE — secure, scoped access from your dashboard

🔔

Never miss a sensitive change

File watch subscriptions

Create named watch rules per repo with gitignore-style glob patterns — plus an optional AI condition — and get @-mentioned in a PR comment when a matching file changes.

Named rules with your own gitignore-style globs, per repo
Optional AI condition: only notify me when it matters
Notifies on PR open and ready-for-review; skips the author, current reviewers, and formatting-only diffs

Start safely. Automate when ready.

Pullmaster only acts when you ask it to. Choose how you use it.

Suggest only

Mention @pullmasterai suggest in a PR comment to get a reviewer recommendation and explanation. Pullmaster does not request a review on GitHub.

Assign

Mention @pullmasterai assign to request the best reviewer on GitHub and post an explanation. Optional escalation can route to the next reviewer if a review stalls.

Dashboard only

Use the code areas dashboard for ownership and risk visibility without using PR commands.

MCP only

Connect Cursor, Claude Desktop, or other MCP clients for read-only repo intelligence in your IDE.

Built for private codebases

Pullmaster only accesses repositories you authorize, reads PR metadata and diffs to generate recommendations, and does not store raw source code.

Works with private repositories
No raw source code stored
Derived data deleted on uninstall
Uses GitHub's permission model
Not SOC 2 certified yet

Built with security-conscious defaults for early teams.

Getting started

Most teams are live in under 5 minutes

Install the GitHub App

Add Pullmaster to your organization or personal account and select which repositories to connect. Pullmaster backfills your Git history automatically — no config file required.

Open a pull request

When you open a PR, Pullmaster reads the changed files and scores every eligible teammate on file familiarity, review history, and current workload.

Ask for a reviewer

In a PR comment, mention one of Pullmaster's commands:

@pullmasterai suggest Recommends a reviewer with an explanation. Does not request a review on GitHub.
@pullmasterai assign Requests the reviewer on GitHub and posts an explanation comment.

Go further

Guide ownership with a PULLMASTER file

Use CODEOWNERS-style rules without triggering GitHub auto-requests.

See ownership health on the dashboard

Find bus-factor risk, unowned areas, and knowledge gaps across your repo.

Query your repo from your IDE

Connect Cursor or Claude Desktop over MCP for read-only repo intelligence.

Read the docs for the full setup guide.

Frequently asked questions

: Pullmaster uses its own PULLMASTER file (same format as CODEOWNERS) for path ownership, and learns dynamically from your repo. It does not read CODEOWNERS.
: No -- most teams are live in under 5 minutes. Install the GitHub App, select your repositories, and Pullmaster starts working immediately using your existing Git history.
: Yes. Pullmaster is built for private, production codebases and follows GitHub's permission model strictly. It only accesses repositories you explicitly grant it access to.
: Yes. Pullmaster is free during early access — no credit card required. We'll always have a generous free tier.
: Pullmaster reads PR metadata and diffs to generate suggestions, but never stores your raw source code. Your data is never sold and never used for model training. To generate recommendations, diffs may be processed by the AI providers we use (OpenAI, Anthropic, and VoyageAI), as described in our privacy policy.
: When you uninstall the GitHub App, the derived data tied to your repositories — embeddings, scores, and ownership metrics — is permanently deleted from our servers shortly after. No manual request is needed.
: Pullmaster requests read access to repository contents and pull requests, and write access to post review comments and request reviewers. It follows the principle of least privilege and only accesses what it needs.
: Not yet. We take security seriously and follow best practices, but we have not completed a formal SOC 2 audit at this time. If compliance is a requirement for your team, reach out and we'll share details on our security posture.
: Pullmaster runs on secure cloud infrastructure located in the United States.
: Pullmaster is built by Justin Ko, a US-based software engineer with 20 years of professional experience. Book a call to chat about how Pullmaster can help your team.
: Pullmaster can automatically escalate to the next best reviewer if an assignment goes unanswered past your configured timeout. You control how long to wait and how many escalations are allowed per PR.
: Pullmaster groups your repository into code areas based on file history and structure. Each area gets an ownership health score, bus-factor and concentration metrics, and recommendations for backup reviewers — so you can fix knowledge gaps before they become incidents.
: Yes. Pullmaster exposes an MCP server with read-only tools for ownership metrics, code areas, reviewer expertise, PR intelligence, and more. Connect from your dashboard with OAuth 2.0 with PKCE — no separate install required beyond the GitHub App.

Know who owns your code before the next PR stalls

Install Pullmaster on GitHub and start turning your team's GitHub history into reviewer recommendations, ownership maps, and engineering risk insights.

Install on GitHub Read the docs

Free during early access. No credit card required.

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