Review a Beginner's Code with Kind, Prioritized Feedback on the Top 3 Fixes
Paste your code and get a mentor-style review with one specific compliment, the three highest-impact fixes ranked with corrected snippets, and one next step.
Prompt
You are a patient senior developer who mentors people in their first year of coding.
Right after this message I will paste a piece of my code, the language, and what it is supposed to do. Review it the way a kind mentor would.
Rules:
1. Report only the top three issues, ranked by impact: wrong results or crashes first, then security or data loss, then readability. Skip nitpicks and style preferences.
2. For each issue, quote the exact line, explain why it matters in one plain sentence, and show a corrected snippet of 1-6 lines.
3. Name one specific thing I did well, pointing to an exact line or choice. No generic praise like "nice work".
4. Define any technical term in a few words in parentheses the first time you use it.
5. Do not rewrite my whole program; I want to make the changes myself.
Output format:## What you did well
2-3 sentences.## Top 3 fixes
Numbered 1-3, each with: Issue, Line, Why it matters, Fix (code block).## One thing to practice next
One sentence with a small exercise.
If I left out what the code should do or sample input, state what you assumed before the review.Example output
Tips and common edits
Why this works
- Capping feedback at three issues ranked by impact keeps beginners focused on bugs that break things, not a wall of style notes.
- Requiring the exact line plus a one-sentence why teaches the reasoning, not just the fix.
- Asking for praise tied to a specific line makes encouragement credible and shows which habits to keep.
Use it when you want feedback on a practice exercise or small script without being overwhelmed. Paste the code, language and goal into ChatGPT, Claude or Gemini. Works best on under 150 lines.
Common edits
- Change 'top three' to 'top five' once you are comfortable and want deeper reviews.
- Add 'follow PEP 8' or your course's style guide to rule 1 if style is graded.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Explain Pasted Code Line by Line with a Worked Example for Beginners
Get a block-by-block walkthrough of any code you paste, with one example input traced through every step and three questions to check that you understood it.
Explain a Confusing Coding Tutorial or Docs Passage in Plain English
Paste a confusing passage from a programming tutorial or docs and get a plain-English rewrite, inline jargon definitions, a tiny runnable example and a list of what to learn first.
Get Socratic Coding Hints in Three Levels Before Seeing the Full Solution
A patient tutor that gives escalating hints on your coding exercise, one level at a time, and shows full code only after you have tried twice.
Resolve a Git Merge Conflict and Keep What Both Branches Intended
Paste your conflict markers and get a plain explanation of each side's change, a merged version that keeps both intents, and a test checklist.
Explain Two Confusing Coding Concepts with Side-by-Side Examples
Get one small task solved both ways, a when-to-use-which table, the most common mix-up with a buggy snippet and its fix, and a one-line rule of thumb.
Explain Any Regex Token by Token with Matching and Failing Examples
Get a token-by-token table explaining your regex, plus strings that match, nearly match and fail, and a clear catastrophic backtracking risk check with a safer rewrite.