Written code review guidelines for the team
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most review friction comes from unspoken expectations: one reviewer blocks on naming, another approves anything that compiles, and authors cannot tell which standard applies today.
First tasks
- Collect any existing review rules from the wiki, chat pins and the contributing file
- Ask the agent to draft a two-page guideline from those notes and your team's stack
- Circulate the draft and ask every regular reviewer for three comments
- Agree the final wording in the next team meeting and commit it