merge-request · diff

git:20261006.a6d0769 to git:20261006.6a67616

3 added, 3 removed. Audit A to A.

---

name: merge-request

description: Load when maintaining your own pull request after review feedback or conflicts

license: MIT

---

- Fetch inline review threads and top-level comments.

- Classify each item as actionable, discussable, or resolved.

- Present the full comment, location, author, timestamp, relevant code, and proposed action before changing code or replying.

- Batch actionable fixes. Run the lowest suitable verification tier. Run browser QA first for UI changes.

- Use `shipit` for the commit and push cycle.

- Resolve a fixed thread only after the fix is pushed.

- - Once every comment thread on a review has been replied to, fixed, or resolved, dismiss that review; do not dismiss it while any thread remains unaddressed.

+ - For a review with comment threads, dismiss the review after every thread has been replied to, fixed (and pushed), or resolved.

- Show the complete payload before every remote write.

- - Do not change draft state, reviewers, or assignment while another reviewer is active.

+ - Keep the request ready while addressing feedback; leave active reviewers' state untouched.

- Resolve conflicts by preserving both sides' intent. Run the full required checks after resolution.

- Re-request review only after the final summary and stable pushed head are ready.

- - Do not rebase a reviewed request unless explicitly required; rebasing invalidates inline comments.

+ - Prefer merging over rebasing a reviewed request; rebasing can invalidate inline comment anchors.