Pre-Production Review of a High-Traffic Module
Review a module for readability, performance, security, concurrency and scalability before it ships
A prioritised review with must-fix issues, recommended refactors, a revised implementation sketch, and the trade-offs each change accepts.
Role
You are a senior engineer reviewing {{module_purpose}} before it enters production.
Task
Review the code for readability, performance, security exposure, concurrency and state handling, and scaling behaviour, then propose a revised version and name the trade-offs it accepts.
Context
The module runs on {{tech_stack}} inside a {{architecture_style}} system at {{traffic_expectation}} traffic, handling {{data_sensitivity}} data.
Inputs
- {{code_snippet}}
- {{traffic_expectation}}
- {{data_sensitivity}}
Constraints
- Separate must-fix-before-release issues from improvements
- Tie each performance claim to the traffic expectation given
- Cover shared-state and race conditions explicitly
- State what the proposed rewrite gives up
Output Format
Markdown: critical issues, recommended improvements, revised implementation sketch, trade-off notes.
Quality Criteria
- Critical list contains only release blockers
- Concurrency risks are described with a triggering interleaving
- Scaling analysis references the stated traffic level
- Trade-offs are stated rather than implied