Product review for every pull request.
Prelint keeps your team aligned, your specs consistent, and your stakeholders informed — automatically, on every PR.
no credit card required · 7 day free trial
const fare = calculateFare(ride);+ booking.amount = forex.convert(+ fare, vendor.currency, customer.currency+ );+ booking.currency = customer.currency;
FX risk on advance bookings
This converts the fare to customer.currency at today's rate and stores it as the charge amount. Vendor settlement still runs in vendor.currency at fulfillment. On advance bookings the exchange rate drifts and the platform absorbs the difference.
Notion — Pricing: International Settlements — “Always store the charge in vendor currency. Show the customer a converted estimate at booking time.”
Suggested fix: store fare in vendor.currency as the charge amount. Use the converted customer amount for display only.
Teams using Prelint
Build fast and stay aligned
AI accelerates development. Prelint makes sure every feature stays consistent, aligned, and true to your product vision.
Product coherence
Every spec, every technology choice, always consistent across your entire product. Prelint connects the dots so your team can move fast with confidence.
Living specifications
Specs live in your repo, reviewed on every PR. Always current, always version-controlled, always the single source of truth.
Stakeholder clarity
Anyone can ask why a decision was made and get an instant, grounded answer. Full context, always available, without pulling engineers out of flow.
Greptile reviews your code.
Prelint reviews your product.
Automatic product specification reviews on every pull request. The same workflow your engineers already use.
PR level product review
Store your product specs in GitHub. Every PR that changes them gets an automatic review. Prelint checks for consistency, completeness, and alignment with existing decisions.
Drift detection
Prelint understands your full product context. It catches when new specs contradict existing ones, when technology choices conflict, or when features duplicate effort.
MCP for stakeholders
Business stakeholders get a sparring partner. Ask "why did we build it this way?" or "has this been considered?" without interrupting engineering.
Your stakeholders get answers.
Your engineers stay focused.
Stakeholders get instant, grounded answers from your product specs — and engineers stay in flow.
Can we add SSO? Losing deals over this
Inboxto product, engineering
Hey team — just got off calls with Meridian Health and DataVault. Both said SSO is a hard requirement for procurement to sign off. That's two enterprise deals stuck in legal.
Can we just add Google login as a quick win? Should check the box for SSO and unblock both of these. I know Lukas looked at auth stuff last quarter so maybe there's something we can reuse.
Happy to jump on a call if it helps.
Mark
to product, engineering, Mark
Hey Mark — great flag on the urgency here. A couple of things worth knowing before the team goes down the Google OAuth path:
Google OAuth won't unblock these deals
Meridian and DataVault both use Okta internally. When enterprise procurement says “SSO,” they mean SAML/OIDC federation with their identity provider — not social login. Google OAuth wouldn't pass their security review. This came up in the Meridian requirements doc spec-enterprise-auth.md, §3.2.
There's already a faster path
Lukas's team specced out SAML + OIDC support in January spec-auth-v2.md. The foundation — service account refactor — shipped last sprint. Lisa estimated 2 weeks to production-ready SAML, which is probably faster than building a Google OAuth flow that wouldn't solve the actual problem.
Your timing is perfect though
Two blocked deals in one week is exactly the kind of signal that helps the team prioritize. If you drop the deal values into #product-priorities, that gives Lisa the ammunition to pull SAML forward in the sprint.
Three steps. Same workflow.
No new tools to learn. Prelint fits into how you already work.
Store specs in your repository
Keep product specifications in GitHub or GitLab alongside your code. Markdown, YAML, or any structured format. Version controlled. Reviewable. Single source of truth.
Open a pull request
Change a spec, add a feature, update a decision. Open a PR like you normally would. Prelint activates automatically.
Get product review in minutes
Prelint reviews the change against your entire product context. Inline comments flag drift, conflicts, and gaps. Approve with confidence.
Full-stack review coverage
CODE REVIEW
- Bugs caught in code
- Code patterns enforced
- Security issues flagged
CODE REVIEW + PRELINT
- Everything in code review, plus...
- Product specs reviewed on every PR
- Cross-spec consistency verified
- Technology decisions tracked
- Business context accessible via MCP
- Full decision history preserved
Start reviewing product specs today
Set up in minutes. Prelint integrates with your existing GitHub workflow and starts reviewing on your next pull request.
no credit card required · 7 day free trial