Plumbcode checks each PR against your team’s written principles and flags where the code or commit message doesn’t hold up, citing the exact rule and the exact lines.
Advisory by default · Minimal GitHub permissions · Set up in minutes
Review summary
3 files changed · +64 −12
Direct database access in a route handler
Violates R-02 · app/api/export/route.ts
New endpoint has no test
Violates R-03 · app/api/export/route.ts
+ export async function GET() {- const rows = await prisma.user.findMany()+ const rows = await getUsers()+ return Response.json(rows)+ }Direct database access belongs in the data layer. Use /lib/db instead of calling Prisma from a route handler.
See the cited ruleTrusted by engineering teams in early access
Repositories connected
Pull requests reviewed
Rule checks run
Teams in early access
01 · The problem
Human review is where standards are supposed to be enforced, but it doesn’t scale with the team, and it’s never consistent.
Plumbcode makes the standard something every PR is checked against automatically.
Your standards sit in a wiki or a CONTRIBUTING file. New hires skim them once, and reviewers can't be expected to remember every line.
One reviewer enforces naming conventions, another cares about commit messages, a third is rushing. The same PR gets different feedback depending on who picks it up.
A commit message that doesn't match the diff, or a rule quietly broken, gets noticed in an incident review rather than in the PR where it was cheap to fix.
02 · How it works
Three steps, no pipeline changes, and nothing to host.
Pick the repositories you want covered. Plumbcode asks for the minimum permissions it needs to read a PR and post a check run, nothing more.
Install Plumbcode
on your organization
Repositories
Paste or upload your standards as Markdown. Give each rule an ID so every finding can point back to exactly the rule it came from.
## R-01 Commit messages describe the change
The message must match what the diff does.
## R-02 No direct database access in route handlers
Use the data layer in /lib/db instead.
## R-03 Every new endpoint has a test
Add or update a file under /tests.Each pull request is checked against your rules. Findings cite the rule and the exact lines, so a developer can accept or dismiss them in seconds.
Add user export endpoint
#128 · acme/api
Direct database access in a route handler
Violates R-02 · app/api/export/route.ts
- const rows = await prisma.user.findMany()+ const rows = await getUsers()Advisory · the PR can still be merged
03 · The product
No vague suggestions. Every comment is traceable to a rule you wrote.
Every finding points to the exact principle it came from and the exact lines of the diff. Developers can accept or dismiss it in seconds.
Add user export endpoint
#128 · acme/api · 3 files changed
Direct database access in a route handler
Violates R-02 · app/api/export/route.ts
- const rows = await prisma.user.findMany()+ const rows = await getUsers()New endpoint has no test
Violates R-03 · app/api/export/route.ts
+ // add tests/export.test.tsInteractive preview — switch tabs to compare views
Security & privacy
Here is exactly what Plumbcode can access, what leaves GitHub, and what we keep.
What happens to a pull request
A webhook tells Plumbcode a pull request was opened or updated.
It fetches the diff and commit messages, and loads your principles.
Only that diff, those messages and your rules are sent to the model.
Results are posted as a check run and comment. The diff is discarded.
Diff not storedGitHub permissions
Identify the repository and PR.
Fetch the diff and commit messages.
Read the PR and post one comment.
Report results as a check run.
Four scopes, listed above. No access to secrets, settings, or repositories you don't select.
Diffs are processed to produce findings and then discarded. We store results, not source.
Data is encrypted in transit and at rest, and access tokens are short-lived.
Enable Plumbcode per repository, and remove it from any repo at any time.
Plumbcode warns. It never auto-merges, never blocks a merge, and never pushes code.
Uninstalling stops all access, and you can ask us to delete your stored findings and rules.
Enterprise controls we’ll build alongside our first customers.
05 · Pricing
Start free on a few repositories. Upgrade when your whole team depends on it.
For small teams and open-source projects getting started.
For engineering teams that want standards enforced everywhere.
For organizations with security and compliance requirements.
Early-access teams get Team free while we shape the product with them. Talk to us
No. Plumbcode is advisory. It posts a check run and a comment with its findings, and the PR can still be merged. Blocking is something we'd only offer as an opt-in once teams trust the results.
Get started
Install the GitHub App, add your principles, and see your first finding on the next PR.
Advisory by default · Minimal GitHub permissions