Write a complete code review checklist for a team

You are an engineering manager who has run code reviews for large teams.
I work in IT & Software: a software company that ships a SaaS product. This work matters to engineering leads, developers and IT buyers.

## Goal
Create a code review checklist and process my team can use on every pull request, so reviews are fast, consistent and catch real problems.

## What matters in IT & Software
- Rules and standards that usually apply: data-protection law (GDPR in the EU, the DPDP Act 2023 in India, CCPA in California); SOC 2 or ISO 27001 security audits; OWASP secure-coding practice; open-source licence terms; the uptime and support promises in customer SLAs.
- Common risks to plan for: outages; data breaches and security holes; vendor lock-in; scope creep; knowledge held by one person; churn after a bad release.
- Tools commonly used: GitHub or GitLab; Jira; Slack; AWS, Azure or GCP; Datadog or Grafana; PostgreSQL or MySQL.
- Words people in this field use: SaaS; multi-tenant; SLA; incident; sprint; release; tech debt; API; ARR.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Languages and frameworks we use: [STACK]
- Team size and experience: [TEAM]
- Problems we keep shipping: [e.g. missing tests, slow queries, security bugs]
- Current review process: [HOW REVIEWS WORK NOW]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the technical problem, the constraints (language, framework, versions, runtime) and what "done" means. List what you need to see that I have not given you.
2. Group checks by area: correctness, readability, tests, security, performance, data and migrations, observability, accessibility.
3. Mark each check as must-fix or suggestion.
4. Add stack-specific checks for my languages and frameworks.
5. Write a pull request template authors fill before asking for review.
6. Set review rules: size limits, response times, number of approvers.
7. Write guidance on giving kind, specific review comments with examples.
8. List the edge cases, failure modes and security risks you considered, and how the solution handles each.
9. Explain how to verify the result: the exact commands, tests or checks to run, and what a pass looks like.

## What to deliver
- The checklist grouped by area
- A pull request template
- Review rules and service levels
- Ten example review comments, good and bad
- A one-page guide for new reviewers

## Expert rules
- Write production-quality code: clear names, small functions, error handling, no placeholder comments such as "..." or TODO.
- Prefer the standard library and the tools already in my stack; justify any new dependency in one line.
- Never weaken security for convenience: validate input, use parameterised queries, keep secrets out of code.
- Respect uptime, security and data-protection requirements. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Put each file in its own fenced code block, headed with its full path.
- Explain decisions in short bullets after the code, not as long paragraphs.
- If the answer is long, give a one-paragraph summary first.

## Before you answer
Check your draft against this list and fix anything that fails:
- The code works as written: no invented libraries, functions or APIs, and versions are named where they matter.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on deployment frequency and uptime.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.