Review a pull request, diff or file against the clean-code standard: find design flaws, magic values, oversized functions, hidden side effects, swallowed errors and missing tests - then write severity-graded review comments (blocker / should / nit) that point at the exact line. Use when the user says "review this code", "check my PR", "look at the diff before merge", "assess code quality", when a PR is about to be opened, or when a team needs review criteria and a rubric.
