Write a code review process for a [language/framework] team. Include: checklist, required reviewer roles, merge criteria, common pitfalls, and communication guidelines.
Useful prompt but the real issue is bigger? That usually means the workflow or team mechanism needs attention, not just the wording.
Sets consistent, quality-focused standards for any dev teamβpromotes learning and lowers bugs.
Checklist: Tests pass, clear naming, no secrets. Roles: Author, reviewer. Merge: 1 approval. Pitfall: N+1 queries...
Log in to suggest improvements.