# Code reviews Code reviews are a fundamental part of ensuring what we deliver works well and adheres to our style guides and quality control standards. Each pull request needs to be reviewed and signed-off by a team member. While reviewing a pull request please ensure you follow these guidelines: * **Take time**: Never review in a hurry. It's a recipe for disaster. * **Test**: Pull the branch locally and test the feature. If you see the feature in action you will be able to review it better. * **Read the description**: Ensure the pull request has a brief description of the feature or enhancement. It's very important to get context from the author's perspective. * **Be positive**: We're all on the same team. Any kind of slander or provocation is not okay. * **Ask questions**: If something isn't making sense seek an answer from the author. * **Legibility**: Legible code is more reusable and future-proof. The author will always feel like it's readable but you as the reviewer are the real judge of this. Everything in terms of variable names, function names, class names, and modules should be understandable. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://playbook.wednesday.is/engineering-playbook/release-and-delivery/code-reviews.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.