@@ -168,6 +168,7 @@ Output only qualifying candidates, with: ref, surface, proof, cause, fix sketch,
168168169169- Start every PR review with 1-3 plain sentences explaining what the change does and why it matters. Put this before `Findings`.
170170- Then list findings first. If none, say `No blocking findings` or `No findings`.
171+- Show size near the top as `LOC: +<additions>/-<deletions> (<changedFiles> files)`, using live PR stats or local diff stats.
171172- Always answer: bug/behavior being fixed, PR/issue URL and affected surface, provenance for regressions when traceable, and best-fix verdict.
172173- For bug/regression fixes, include a compact `Provenance:` line after cause/root-cause when a bounded history pass can identify it. Use `git log -S/-G`, `git blame`, linked PRs/issues, and tests.
173174- Provenance must separate roles when they differ: blamed code author username, blamed PR author username, blamed PR merger/committer username, automerge trigger when known, current PR author username, PR number, and date. Do not collapse them into one "introduced by" actor.
@@ -176,6 +177,13 @@ Output only qualifying candidates, with: ref, surface, proof, cause, fix sketch,
176177- Phrase provenance as `introduced by`, `made visible by`, or `carried forward by`, with confidence (`clear`, `likely`, `unknown`). If unclear, say what evidence is missing instead of guessing. For features, docs, and refactors, use `Provenance: N/A` or omit it when no broken behavior is being fixed.
177178- Keep summaries compact, but include enough proof that the verdict is auditable without rereading the PR.
178179180+LOC proof:
181+182+```bash
183+gh pr view <number> --json additions,deletions,changedFiles \
184+ --jq '"LOC: +\(.additions)/-\(.deletions) (\(.changedFiles) files)"'
185+```
186+179187## Read beyond the diff
180188181189- Review the surrounding code path, not just changed lines. Open the caller, callee, data contracts, adjacent tests, and owner module.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。