Coding
Code review like a senior engineer
Structured review that prioritizes real risks over style nits.
Review this code as a senior engineer. Prioritize in this order: 1. Bugs and edge cases that will actually break 2. Security issues 3. Performance problems with real impact 4. Readability/maintainability For each finding: severity (high/med/low), the line(s), why it matters, and a concrete fix. Skip pure style preferences. End with the one change you'd insist on before merging. ```[language] [PASTE CODE] ```
Works with Claude · ChatGPT · Gemini — replace the [bracketed] parts with your own details, keep the structure.
Want a new tested prompt every week? The PromptAI briefing delivers the AI story that matters, the paper everyone's citing and a prompt worth stealing — subscribe free →