Prompt · Code & Agents
Code Review Partner
Paste one file or change and get a merge call, real defects ranked by impact with the input that triggers each, fixes re-checked against every finding, and what the reviewer still needs to see.
Use it when
- You work alone or on a small team and want a second pair of eyes before you merge.
- You are learning a language and want to see why something breaks, with the fixed lines.
- You inherited code and need to separate what is risky from what is only untidy.
Skip it when
- You need a security audit or compliance sign-off. This is a general review, not a replacement for specialised tools or an expert.
- The change spans many files that the model cannot see. Use a coding agent with repository access (the PR Reviewer skill), or paste the callers too.
Example
Input: [CONTEXT] = "JavaScript, a habit-tracking web app. Shows the user's current practice streak on the home screen." [PASTE CODE]:
// streak.js
1 // days: "YYYY-MM-DD" strings, one per practice session, oldest first
2 export function currentStreak(days) {
3 let streak = 0;
4 const expected = new Date();
5 for (let i = days.length - 1; i >= 0; i--) {
6 if (days[i] !== expected.toISOString().slice(0, 10)) break;
7 streak++;
8 expected.setDate(expected.getDate() - 1);
9 }
10 return streak;
11 }Output excerpt:
Verdict
FIX FIRST: the streak is wrong for anyone outside UTC near midnight and for anyone who practises twice in a day.
Critical (breaks things)
streak.js:6 and :8 mix calendars.
toISOString()gives the UTC date whilesetDatemoves the local date, so in UTC+2 between 00:00 and 02:00 today's session never matches and the streak shows 0. Fix: compare local dates. Findings 1-3 all touch this function, so here it is whole:const localDay = (d) =>
${d.getFullYear()}-${String(d.getMonth() + 1).padStart(2, "0")}-${String(d.getDate()).padStart(2, "0")};export function currentStreak(days, now = new Date()) {
const seen = new Set(days);
const day = new Date(now);
if (!seen.has(localDay(day))) day.setDate(day.getDate() - 1);
let streak = 0;
while (seen.has(localDay(day))) {
streak++;
day.setDate(day.getDate() - 1);
}
return streak;
}Re-checked against 1-3: local dates on both sides, duplicates collapse in the Set, and input order no longer matters.
streak.js:5-9: two sessions on one day break the loop. With days ending "D-1, D, D", the second "D" is compared with yesterday, so the streak is 1 instead of 2. Fixed by the Set in the function under 1.
streak.js:4: if the user has not practised yet today, the streak shows 0 although yesterday's run is still alive. If a streak should last until the day ends, start from yesterday when today is missing: the
ifline in the function under 1.
Need to see
- How
daysis written: if it stores UTC dates rather than the user's local dates, finding 1 changes andlocalDaymust use the UTC getters. - Whether the streak should survive until the day ends (assumed yes in finding 3).
Illustrative example written by Meevra to show the target format; your model's wording will differ.
What is inside
The full prompt has these sections. The ones marked “in the pack” come with the download.
- What it does in the pack
- Use it when on this page
- Skip it when on this page
- The prompt in the pack
- How to use in the pack
- How to run (Oct 2026) in the pack
- Example on this page
- Troubleshooting in the pack
Get Code Review Partner
The full prompt is a file you keep and reuse: the checklist and the answer format written out, with how to run it on each model. It comes in the Code & Agents pack (5 prompts · 15 skills · 1 free), with a QUICKSTART, setup notes in every item and 12 months of updates.
All-Access 39 € vs 7 packs × 12 € = 84 € · less than buying 4 or more packs one by one
Stuck? Email support@meevra.com — we'll help you set it up.