lead-review
Lead Review
Review a PR as its tech lead. To review commits that reached a branch without a PR (a range, or one author's commits in it), follow these steps with the changes in references/audit.md.
What backs a finding sets its severity:
| Severity | Backed by | Can the author argue? |
|---|---|---|
| BLOCKER | Proof (a reproduction you ran, or a file:line trace), or a written project rule quoted verbatim |
No |
| NIT | Neither. It is your preference. | Yes. The author may decline it with a reason. |
| QUESTION | A suspicion that only the author can settle | Not yet. The answer decides. |
Written rules are the checklist, the coding standard, CLAUDE.md/AGENTS.md, specs, ADRs, AC THEN clauses and the PR template. The script enforces the table: a finding with Rule or Proof must be a BLOCKER, and a NIT has neither. Never remove a Rule or Proof to lower a severity. A NIT you raise on PR after PR belongs in a written rule. Write the rule, or stop raising it.
Every review body has the same shape in every round. scripts/review_body.py builds the skeleton and checks the result. Do not post a body that the script rejects.
Paths in this file are relative to the directory that holds this SKILL.md. Find that directory first, then call each script by its absolute path, because the shell runs in the repo. Use python3. The scripts need only the standard library.