PullMentor - AI Code Review Coach That Teaches, Not Just Criticizes

Junior developers dread code reviews — cryptic comments like 'use const not let' leave them confused. PullMentor watches GitHub PRs, generates kind but detailed reviews explaining the 'why' behind suggestions, links to relevant docs, and suggests concrete fixes. Code reviews that mentor instead of gatekeep.

𝕏 Post Reddit HN

Difficulty

beginner

What is it?

A junior dev opens a PR, expects feedback, and gets a one-liner: 'this breaks DRY principles.' They don't know what to fix. PullMentor changes this: when a PR is opened in a repo that has it installed, Claude analyzes the code diff and generates reviews that explain (1) what could be better, (2) why it matters, (3) how to fix it with code examples, (4) links to relevant docs (MDN, official repos). The tone is encouraging, not gatekeeping. A junior can read a PullMentor review and actually learn something. Built as a GitHub App that listens for PR events, fetches the diff, sends to Claude API with a mentor-style prompt, and posts a review comment. The core insight is that reviews that teach create better engineers faster. Why 100% buildable right now: GitHub App APIs are stable, Claude's code understanding is excellent, and the entire flow (listen for PR -> fetch diff -> Claude analyze -> post comment) is straightforward. No complex infrastructure needed — Vercel Functions handle the webhook, Supabase stores PR history for context, and Claude handles all the reasoning.

Why now?

GitHub Apps are now mature and common; Claude's code understanding is production-ready; developer mentoring and junior dev onboarding is peak focus in 2025; code review friction is a well-known bottleneck.

▸GitHub App OAuth and webhook setup (Implementation: GitHub App registration, Vercel webhook handler)
▸PR diff fetcher (Implementation: Octokit to get PR files + changes, parse unified diff)
▸Claude-powered mentor-style review generator (Implementation: Claude API with system prompt emphasizing teaching, not gatekeeping)
▸GitHub PR comment poster (Implementation: Octokit comment API)
▸Settings UI to customize review style and intensity (Implementation: Next.js form, Supabase settings table)

Target Audience

500+ teams (5–50 engineers) with junior developers learning to code, especially bootcamp grads and early-career developers. Primary user: tech leads or engineering managers.

Example Use Case

Emma is an engineering lead at a 10-person startup with 3 junior devs fresh from a bootcamp. Code reviews are slow — Emma has to explain every pattern, and juniors feel criticized. She installs PullMentor. Now when a junior opens a PR with inefficient loops or poor naming, PullMentor leaves a comment: 'You're using a nested loop here — it works but for N items this is O(n²) time complexity. For large datasets this gets slow. Use a Set to track seen items instead — here's the pattern: [code example]. Read more: [link to Big O guide].' Juniors learn from every PR. Code quality improves faster.

User Stories

▸As a junior developer, I want code review feedback that explains the 'why' behind suggestions, so that I learn from reviews instead of feeling criticized. As an engineering lead, I want to scale code review teaching across my team without spending hours writing explanations, so that juniors get consistent mentoring.
▸As a senior engineer, I want code reviews to be educational, not gatekeeping, so that my team grows faster and review cycles are more positive.

Acceptance Criteria

GitHub OAuth: done when app installs and webhook events are received. PR Detection: done when app triggers on new PRs and fetches diffs. Claude Review: done when review is generated with explanation, code example, and doc link. Comment Post: done when review posts as GitHub comment with proper formatting. Settings: done when custom review style is applied to generated reviews.

Is it worth building?

$19/month × 70 teams = $1,330 MRR at month 2. $49/month × 150 teams = $7,350 MRR at month 5.

Unit Economics

CAC: $0 (ProductHunt, organic GitHub). LTV: $228 (12 months at $19/month average). Payback: immediate. Gross margin: 88% (Claude API cost is lowest among competitors).

Business Model

SaaS subscription per GitHub organization.

Monetization Path

Free tier (1 PR per day reviewed). $19/month (unlimited PRs, detailed explanations). $49/month (unlimited PRs, custom review style, Slack summaries, team analytics).

Revenue Timeline

First dollar: week 3. $1k MRR: month 2. $5k MRR: month 5.

Estimated Monthly Cost

Claude API: $30 (assume 100 PRs/day at $0.01 per request). GitHub API: free tier. Vercel: $20. Supabase: $25. Resend: $15. Sentry: $29. Total: ~$119/month.

Profit Potential

Sustainable at $1.5k–$6k MRR with minimal hosting costs.

Scalability

High — can expand to Gitlab support, custom linter integration, team analytics dashboards, and training dashboards.

Success Metrics

Week 1: 150 GitHub installs. Week 2: 15 paid teams. Month 2: 50 paid teams, 75% retention.

Launch & Validation Plan

Interview 20 engineering leads about code review friction points, post prototype on ProductHunt, recruit 8 teams for beta with junior developers, have seniors rate review quality, track engagement (does the reviewer act on the suggestion?).

Customer Acquisition Strategy

First customer: reach out to 20 startups on Angel List and Twitter/X with free 30-day trial. Then: ProductHunt launch, r/developersettings post, GitHub Marketplace listing, tweet examples of good vs. bad reviews.

What's the competition?

Competition Level

Medium

What's the roadmap?

Feature Roadmap

V1 (launch): GitHub App OAuth, PR diff fetch, Claude mentor review, GitHub comment post, basic settings. V2 (week 3–4): custom tone/style settings, ignore patterns, Slack digest, team analytics. V3 (month 2+): Gitlab support, custom linter rules, training dashboard, team reporting.

Milestone Plan

Phase 1 (Week 1–2): GitHub App registered, webhook handler working, Claude review generation tested on sample diffs. Done when bot successfully reviews a test PR. Phase 2 (Week 3–4): settings UI complete, comment formatting polished, error handling for API failures, landing page optimized. Done when beta teams can install and use without issues. Phase 3 (Month 2): Sentry monitoring live, analytics ready, ProductHunt launch, GitHub Marketplace submission. Done when 40+ orgs on paid tier.

How do you build it?

Tech Stack

Next.js, GitHub App SDK, Claude API, Supabase, Stripe, Resend, Octokit — build with Cursor for webhook handler, Lovable for settings UI, v0 for review templates.

Time to Ship

2 weeks

Required Skills

GitHub App webhooks, Claude API, Next.js, basic git diff parsing.

Resources

GitHub Apps docs, Octokit.js, Claude API, Next.js serverless functions, Supabase quickstart.

MVP Scope

GitHub App manifest with webhook for pull_request events. Backend: /api/github-webhook (listens for PR, fetches diff, calls Claude). Pages: /login (GitHub OAuth), /settings (customize review style). DB: installations (one per org), pr_reviews (history), settings. Claude prompt template for mentor-style review.

Core User Journey

Click 'Install on GitHub' -> authorize org -> next PR is reviewed automatically -> team reads review -> implements suggestion -> aha moment -> upgrades to paid.

Architecture Pattern

GitHub webhook (PR opened) -> Vercel Function receives event -> Octokit fetches PR diff -> diff passed to Claude -> Claude generates mentoring review -> Octokit posts comment on PR -> review logged in Supabase.

Data Model

GitHubOrg has one Installation and many PRReviews. PRReview has one SourcePR (external GitHub ID) and many ReviewComments.

Integration Points

GitHub API (webhooks, PR details, comments), Claude API for review generation, Stripe for payments, Supabase for storing review history and settings, Resend for email notifications.

V1 Scope Boundaries

V1 excludes: GitHub org admin analytics, multi-repo stats, custom training data, integration with Slack/Discord, support for other platforms (Gitlab, Bitbucket in V2).

Success Definition

An engineering team installs the app, receives a review on their next PR, reads it, learns something, and implements the suggestion without being told to.

Challenges

Avoiding false positives is critical — bad reviews tank retention. Claude sometimes suggests overkill refactoring for simple code. Managing PR comment volume (one comment per file or one per PR) requires thoughtful design.

Avoid These Pitfalls

Do not attempt to review every single line — pick the most impactful 3–5 suggestions per PR or reviews get too long and ignored. Do not suggest refactoring for micro-optimizations (e.g., 'use i++ not ++i') — focus on learning and safety. Do not post reviews that could discourage junior devs; filter out overly critical Claude outputs with a human-in-the-loop or sentiment check.

Security Requirements

Auth: GitHub OAuth. RLS: orgs can only view their own PR reviews. Rate limiting: 50 req/min per organization (GitHub API limits). API keys: GitHub access token stored encrypted in Supabase Vault. Input validation: PR diffs sanitized. GDPR: data deletion endpoint removes org reviews on request.

Infrastructure Plan

Hosting: Vercel. Database: Supabase (Postgres). Webhooks: Vercel Functions. CI/CD: GitHub Actions. Cron jobs: none. Monitoring: Sentry for errors, Vercel Analytics. Cost: Vercel $20, Supabase $25, Resend $15, Sentry $29, Claude API $30. Total: ~$119/month.

Performance Targets

Expected DAU at launch: 30 orgs. Requests per day: 200 (mostly PR reviews). Review generation time: under 10 seconds (Claude API). Comment post: under 2s. Caching: PR diffs cached in Supabase for 24h.

Go-Live Checklist

☐Security: GitHub token handling reviewed, diff sanitization tested
☐Payments: Stripe subscription works
☐Errors: Sentry live
☐Monitoring: Vercel Analytics active
☐Domain: custom domain and SSL
☐Legal: privacy policy, terms, GitHub App privacy policy published
☐Beta: 8 orgs tested, review quality feedback collected
☐Rollback: previous Vercel deployment saved
☐Launch: ProductHunt post ready, Twitter thread with example reviews, r/developersettings post queued.

How to build it, step by step

1. npx create-next-app pullmentor. 2. npm install octokit @anthropic-ai/sdk @supabase/supabase-js stripe resend. 3. Register GitHub App in GitHub settings. 4. Create Vercel Function /api/github-webhook to handle PR events. 5. Implement Octokit call to fetch PR diff. 6. Build Claude prompt for mentor-style review. 7. Implement Octokit call to post review comment on PR. 8. Create /settings page for custom review style. 9. Add Stripe subscription checkout. 10. Deploy and test with test PRs on a GitHub repo.

Generated

March 25, 2026

Model

claude-haiku-4-5-20251001

← Back to All Ideas