Address PR review feedback

This skill is procedural. The governing specification, ROADMAP and AGENTS.md remain authoritative. Do not turn reviewer preferences into new product semantics.

Procedure

1. Verify the live PR and branch. Read the PR state, head branch/head SHA, base branch and current checks from GitHub. Work in the PR's existing dedicated worktree when available; otherwise create a worktree for the PR branch. Never switch the shared checkout merely to address a review.
2. Enumerate every comment surface before editing: top-level review submissions, inline review comments/threads, and issue-level PR comments. Cross-reference duplicates and retain a disposition for each material finding.
3. Classify before fixing.
   • Clear correctness/contract/evidence/documentation defect: fix it.
   • Specification or design question: do not guess; present the decision to the owner and stop that item.
   • MINOR/NIT or preference: fix only when cheap and in scope; never expand the PR to satisfy it.
4. Make evidence-backed fixes. For a behavior defect, add or strengthen a regression test when that test provides real proof. For a documentation/claim defect, verify the corrected claim against the actual code, schema, fixture or pinned evidence rather than inventing a test solely for ceremony. When a material finding exposes a repeated pattern within the changed surface, inspect and fix the same class of occurrence there rather than patching only the cited line; do not widen this into unrelated repository cleanup. Preserve the retained plan and reconciliation for specification-governed work.
5. Validate economically. Run targeted checks while iterating. After the final source-relevant change, run the full AGENTS.md gate once. If the complete fix is documentation-only, use the documentation-only exemption. Any source change after the full gate invalidates that gate.
6. Run the independent self-review when required by AGENTS.md. Invoke .claude/agents/aip-reviewer.md on the complete updated diff unless the change qualifies for the strict documentation-only exemption. Resolve BLOCKER/MAJOR findings; return semantic ambiguities to the owner. After material fixes, rerun affected validation and the reviewer once, not an open-ended nit loop.
7. Stop before commit/push unless explicitly authorized. Asking to "address review feedback" authorizes editing and validation, not committing or pushing. Report the fixes, validation and self-review result, then wait for an explicit owner instruction to commit/push. If that authorization is given, verify the PR head branch, commit/push there only, capture the pushed SHA from git rev-parse HEAD, update the PR body/reconciliation when needed, post one concise summary comment, and re-check all comment surfaces once after the push. Never merge.

Completion condition

Every material review finding is either fixed with evidence or explicitly returned to the owner as a design/specification decision; required validation is green; and any required independent self-review has no BLOCKER/MAJOR findings. If the same material finding is recurring across PRs, report a candidate reusable guard separately rather than expanding the current PR. If commit/push was not explicitly authorized, finish by reporting that the fixes are ready but uncommitted. Leave merge to the owner.