docs: require PR discussion comments in reviews

2026-04-28 06:10:55 +07:00
parent 668b64d594
commit 28224ccb9f
2 changed files with 4 additions and 1 deletions
@@ -70,7 +70,7 @@ All work starts from a Gitea issue. Two phases, each with a dedicated role:
 **Constraint:** Reviewer must NOT edit code on the PR.

 1. Re-read the original issue — verify PR addresses the locked requirement.
-2. Read PR diff and discussion history.
+2. Read PR diff, review history, and PR discussion comments.
 3. Validate in worktree if needed (`.worktrees/pr-<number>`, run `go test`, `go vet`, `gofmt`).
 4. Check for scope creep — FAIL if PR contains unrelated changes or refactoring.
 5. Write verdict — start with **PASS** or **FAIL**.