merge-request · diff

git:20261014.e6467ee to git:20261018.3c9c1cd

2 added, 2 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.

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

- The configured GitHub MCP lacks review dismissal. Use `gh api` through Bash for REST `PUT /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/dismissals` with `{"message": "<reason>", "event": "DISMISS"}`; confirm the returned review `state` is `DISMISSED`.

- On a protected branch, dismissal requires administrator or designated dismissal permission; report a denied dismissal rather than treating thread resolution as equivalent.

- - Preserve the request's draft state while addressing feedback; leave active reviewers' state untouched.

+ - Preserve the request's draft state while addressing feedback; do not mark a draft PR ready to solicit reviews, and leave pending reviewer requests 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.

+ - After the final summary and stable head are pushed, use `shipit` to request or trigger configured bot reviews for that head and re-request only affected completed human reviews—not reviewers still pending. Treat prior-head results as stale; keep the PR draft until shipit's review gates are met, then mark it ready in a separate action.

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