Go peer review compact checklist

Approval Check

Before approving Go code, confirm that the owner and layer are right, the public contract is typed and small, errors are explicit and deterministic, side effects are visible, resources have lifetimes, validation happens before mutation, tests prove both package behavior and user-visible behavior, and documentation matches the code.

If any of those are unclear, the review is not done. Use LLM finding patterns to name the issue and include a concrete improvement rather than a vague request to clean up or refactor.

← LLM finding patterns Guide index Go optimization guide →

Sources

• Go peer review guide
• Testing strategy
• Go optimization guide