Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Find a real, open pull request (in an open-source repo or your own) and write a complete, high-quality review. Your review must: read the diff critically across the right dimensions (correctness/edge cases first, then design, readability, and tests — not just style); write comments that are specific, kind, and ACTIONABLE, each explaining WHY; use Conventional-Comments-style labels (nit/suggestion/issue/question/praise) to signal what's blocking vs optional; include at least one piece of genuine praise; and apply the standard of approving when the change 'improves overall code health' rather than demanding perfection. Submit the review comments plus a short note on your overall recommendation (approve / request changes) and why.
Comments target correctness/design/readability/tests (style left to tooling); each is specific, actionable, and explains why.
Severity labeled (blocking vs nit/optional); kind, curious tone; includes genuine praise; reviews the code, not the person.
Approves on 'improves overall code health', not perfection/personal style; clear, justified recommendation.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# Review a real PR with labeled feedback ## Goal Find a real, open pull request (in an open-source repo or your own) and write a complete, high-quality review. Your review must: read the diff critically across the right dimensions (correctness/edge cases first, then design, readability, and tests — not just style); write comments that are specific, kind, and ACTIONABLE, each explaining WHY; use Conventional-Comments-style labels (nit/suggestion/issue/question/praise) to signal what's blocking vs optional; include at least one piece of genuine praise; and apply the standard of approving when the change 'improves overall code health' rather than demanding perfection. Submit the review comments plus a short note on your overall recommendation (approve / request changes) and why. ## Acceptance criteria - [ ] Substance over style: Comments target correctness/design/readability/tests (style left to tooling); each is specific, actionable, and explains why. - [ ] Feedback craft: Severity labeled (blocking vs nit/optional); kind, curious tone; includes genuine praise; reviews the code, not the person. - [ ] Right standard: Approves on 'improves overall code health', not perfection/personal style; clear, justified recommendation. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.