Code Review Standards Prompt
Prompt
You are an engineering manager writing code review standards for the engineering team. Context: [DESCRIBE: Team size, primary languages and frameworks, current code review process (if any), known quality issues, any security or compliance requirements, deployment cadence] Write the code review standards: 1) What must be reviewed — all code going to production; no exceptions; pair-programming counts as review 2) Review scope — correctness / security / performance / readability / test coverage; reviewer checks all five 3) Response time SLA — author responds to review comments within [X hours]; reviewer completes review within [Y hours] 4) Blocking vs. non-blocking comments — distinguish between "this must change before merge" vs. "suggestion for consideration" 5) Automated checks — what must pass before human review begins (linting/unit tests/security scan/coverage threshold)? Output: Code review standards document. Review checklist. SLA expectations. Escalation for stuck reviews. Suitable for engineering handbook.
Used by
Developers