A new engineer's first pull requests are where they learn how your team really builds software. Mesrai explains the conventions in context, so seniors mentor on design rather than on naming and error handling.
Teams use AI code review to speed up developer onboarding: Mesrai reviews a new engineer's pull requests against the team's rules and memories and explains each convention in context — how errors are handled, which helpers to use, which patterns are deprecated. New hires learn the codebase from real feedback, and senior engineers spend their time on design discussions.
Conventions live in senior engineers' heads and come out one review comment at a time.
New hires wait for reviews from busy people and hesitate to ask basic questions.
Documentation is out of date, so new engineers copy whatever code they find first — including deprecated patterns.
Senior engineers lose days to repetitive feedback during every hiring wave.
Rules and memories turn tribal knowledge into comments that say what to do and why, on the exact line.
Mark old helpers and patterns as deprecated in rules, so new code doesn't copy them.
New hires get answers in minutes without waiting for a senior's review slot.
The repository graph points to existing helpers and related code the new hire didn't know existed.
Illustrative examples of the kind of change teams onboarding new engineers make every week, and the review comment Mesrai would post.
A new engineer writes their own currency formatting in their first week.
const label = `₹${(amount / 100).toFixed(2)}`;We format money with formatMoney() from src/lib/money.ts, which handles currency, locale and paise rounding. toFixed on paise can produce wrong totals for some amounts.
Result: The new hire learns the helper exists, and the bug-prone pattern doesn't spread.
A new engineer copies a data-fetching pattern from an old module.
legacyFetch is deprecated (see memory 'Data fetching'). New code uses the typed apiClient from src/api/client.ts, which adds auth, retries and tracing.
Result: Old patterns stop multiplying through copy-paste.
Follow the team onboarding recipe in the docs; it takes about 30 minutes.
Write memories for the five things every new hire gets wrong — error handling, data fetching, money, dates, logging.
Add rules that mark deprecated helpers and modules.
Ask new hires to resolve Mesrai's comments before requesting human review.
Use 👍 / 👎 reactions so Mesrai learns which comments help.
@mesrai remember: new code fetches data with apiClient from
src/api/client.ts. legacyFetch is deprecated and must not be
used in new files.New hires productive in fewer weeks
Conventions documented as rules and memories
Less repetitive review work for seniors
Deprecated patterns stop spreading
It explains the team's conventions on the new engineer's own code, as soon as they open a pull request, so they learn faster and seniors repeat themselves less.
Facts about your codebase that you teach Mesrai in plain language, for example with '@mesrai remember:' in a pull request comment. They apply to future reviews at the scope you choose.
14-day free trial · every feature unlocked · no credit card required.
A senior-engineer first pass on every pull request, before you can afford to hire one — so a small team ships fast without shipping regressions.
Read more Engineering ManagersShorter review queues, consistent standards across reviewers, and delivery metrics — without adding process or reading every diff yourself.
Read more Enterprise TeamsConsistent review across hundreds of repositories, with SSO, audit logs, self-hosting and your own LLM provider for data control.
Read more