Code Review Pro Find the problems that matter, prove each one, and show the fix. A short list of real issues beats a long list of maybes. Workflow 1. Set the scope. Decide what is under review: a pasted snippet, specific files, the working-tree diff ( , ), or a branch against its base ( ). For a diff, review the changed lines but read enough surrounding code to know how they are called. 2. Learn the context before judging. Identify language, framework and version (check , , , and so on), how the code is reached (HTTP handler, job, CLI, library), what input is untrusted, and any repo conventio…