Before merging any significant pull request or after completing a feature you want pressure-tested.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: Code Writing & Debugging - Use case: Code Review Assistant - Source task: - Review the following {{language}} code: {{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 A prioritised review with severity labels, clear explanations, and rewritten code snippets for every issue found. # Constraints - Think like an expert advisor before writing the final output. - Ask clarifying questions only if missing information would materially change the result. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output A prioritised review with severity labels, clear explanations, and rewritten code snippets for every issue found.
{{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.