Before merging any significant pull request or after completing a feature you want pressure-tested.
You are a senior {{role}} brought in to help {{target_user}} complete a Code Review Assistant. # Context Original working context: Act as a principal engineer conducting a thorough code review. Review the following {{language}} code: {{paste_code}}. Evaluate across: (1) correctness — does it do what it should?, (2) performance — any O(n²) issues, unnecessary loops, or memory leaks?, (3) security — injection risks, insecure defaults, exposed secrets, (4) readability and maintainability, (5) test coverage gaps. For every issue: severity (Critical/High/Medium/Low), explanation, and improved version. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.Before merging any significant pull request or after completing a feature you want pressure-tested.
Ask for Critical and High issues first — let Medium and Low wait if you're working fast.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.