Connect your codebase — get PRDs with real engineering context
PMRead reads your GitHub repository and uses codebase structure, open issues, and recent PRs as context when generating PRDs. Engineering tasks reference actual files and APIs, not generic placeholders.
How it works
1. Connect via GitHub OAuth
Click 'Connect GitHub' in your PMRead project settings. You'll be redirected to GitHub to authorise read access on the repositories you select. No write access is requested.
2. Select a repository
Choose the repository that contains the product you're writing a PRD for. PMRead reads the repo structure, key files, open issues, and recent pull requests.
3. Generate a PRD with codebase context
When you click 'Generate PRD', the codebase summary is included as context. The resulting PRD has engineering tasks that reference real modules, data models, and API endpoints — not 'update the backend'.
Why it matters
Engineering tasks your team will actually use
Without codebase context, PRD engineering tasks read like: 'Update the backend to support the new feature.' With GitHub connected, they read like: 'Add a billing_period field to the users table, update UserOut schema in schemas/user.py, and add a PATCH endpoint in routers/billing.py.' One is skippable. The other is a sprint ticket.
Open issues as an insight source
GitHub issues — especially those labelled 'bug' or 'customer-reported' — are a high-signal feedback source that most PMs never ingest. PMRead reads open issues and surfaces them alongside customer interview insights.
Closes the gap between PM and engineering
The most common sprint planning friction is PMs writing requirements that ignore existing architecture. With codebase context, PMRead catches constraints before the kickoff — reducing back-and-forth by giving engineers a spec that already speaks their language.
Setup guide
Open your PMRead project settings
Navigate to any project → Settings → Integrations → GitHub.
Authorise via GitHub OAuth
Click 'Connect GitHub'. You'll be redirected to GitHub to approve read access. Select which repositories PMRead can access — you can limit it to just the relevant repo.
Select a repository for this project
Back in PMRead, choose the repository that maps to this product. PMRead will index the structure and recent activity.
Generate a PRD — codebase context included automatically
No extra steps. The next time you click 'Generate PRD', GitHub context is included automatically. You'll see engineering tasks reference actual files and APIs.
Frequently asked questions
What data does PMRead read from GitHub?
Repository file structure, key source files (to understand data models and APIs), open issues, and recent pull requests. PMRead does not read secrets, .env files, or files in .gitignore.
Does PMRead get write access to my repository?
No. PMRead requests read-only access (repo scope without write). It never creates issues, PRs, or commits.
Does this work with private repositories?
Yes. GitHub OAuth with the repo scope covers private repositories you own or have access to. You control which repositories PMRead can see during the OAuth flow.
What languages and frameworks does PMRead understand?
PMRead reads code as text, so it works with any language. It's most useful when your codebase has clear file names, models, and API routes — Python/FastAPI, TypeScript/Next.js, Ruby on Rails, Django, and similar structured codebases work well.
Is GitHub integration available on the free plan?
No. GitHub integration requires a Pro plan (₹1,699/mo or $19/mo).
Try PMRead free — no credit card required
Start on the free tier. Upgrade to Pro when you're ready to connect GitHub.
Get started free →Other integrations