Run this quick test after your next AI coding session. Paste this prompt in and clock what score it spits out.
Bet it lands somewhere between 65 and 75.
🔁 The Self-Scoring Loop
Here’s the exact prompt making the rounds on r/PromptEngineering:
- Review the code
- Score the code
- Find issues
- Fix the code
- Re-score the code
- Produce a final confidence report
Then add this line: “Improvise further to achieve a score of 95+. Once the plan is approved, do not stop at review. You must improve the code and increase the score.”
That last part is the whole game. It locks the AI into active fix mode instead of just flagging problems and moving on.
📊 What the Numbers Actually Mean
- Under 80: Real bugs are hiding in there. Don’t ship it.
- 80 to 94: Solid start. Let it keep going.
- 95+: You’re close. Manual review, then ship.
💡 Extra Tips
- Works with Claude Code, OpenAI Codex, and Google AI Studio
- The bigger the codebase, the more value this loop unlocks
- Stuck under 90? Ask it directly: “What’s the single biggest blocker to hitting 95?”
- You can run this on legacy code too, not just freshly generated stuff
🚀 Do it today
Copy the prompt. Paste it after your next generation session. Note your starting score and your ending score.
That gap tells you exactly how much quality AI leaves on the table by default.
After you complete the code generation with Claude Code / OpenAI Codex, Google AI Studio, give this prompt and see the magic?
by u/ishwarjha in PromptEngineering