merging-pull-requests

Merging a Kivgraph pull request

This skill performs the final, destructive PR operation. A request to merge a specific PR authorizes both the merge and deletion of that PR's head branch. Do not use this skill for requests to prepare a PR, check whether it is ready, or enable auto-merge. The workflow below is self-contained and must not load another skill's SKILL.md at runtime.

Preconditions

1. Treat the PR as review-ready only when the intended changes are committed and pushed, relevant local gates have passed, required GitHub checks have completed successfully, CodeRabbit has reviewed the latest head, every actionable finding is addressed or explained, and GitHub reports no merge conflict or other known blocker. Stop if any condition is missing; do not merge around an unresolved finding.
2. Resolve exactly one PR. Use the PR number or URL supplied by the user; if it is absent, use the current branch's PR only when there is exactly one. Stop if the target is ambiguous.
3. Fetch live PR metadata from GitHub. Confirm that the PR is open, not a draft, mergeable, and has a concrete headRefOid, headRefName, headRepository.nameWithOwner, base branch, and repository. Never infer these values from a stale local checkout.
4. Check required status checks and review state. Wait for pending checks and CodeRabbit; stop on a failure, conflict, missing required check, or a review decision that still requests changes.

CodeRabbit final gate

The final gate is about the current head SHA, not merely whether CodeRabbit has reviewed the PR at some point.

1. Before waiting, record the current head SHA and a snapshot of all existing CodeRabbit reviews, inline comments, issue comments, and thread states. Keep each artifact's ID, commit or timestamp fields, body digest, and resolution state where available. Set reviewCycleStartedAt immediately after this snapshot. Identify the bot by its GitHub account/login returned by the API, not by a string in the comment body. The usual login is coderabbitai[bot], but do not assume it.
2. Wait until the CodeRabbit check or review for that exact SHA has completed. A queued, in-progress, absent, or API-inaccessible review is a blocker.
3. Fetch all three surfaces again:
   • pull-request reviews;
   • pull-request review comments, including replies and threads;
   • issue comments on the PR, which cover comments outside the diff.
4. Compare the second snapshot with the first and save the second as the postReviewSnapshot. Any new CodeRabbit finding that requests a change blocks the merge, even if CI is green. A new clean summary is not a finding, but it must be reported.
5. Check existing findings as well. Every CodeRabbit comment concerning the current head must be resolved, obsolete with an evidence-based explanation, or already fixed. Do not treat an old comment as harmless just because it was posted on an earlier SHA. Unresolved review threads or a CHANGES_REQUESTED review block the merge.
6. Issue comments do not expose commit_id. Treat an issue comment as part of the current review cycle when its ID is new after reviewCycleStartedAt, or its body or updated_at changed after that checkpoint. Evaluate its body and ID even without a commit field. Pre-existing unchanged issue comments remain historical, but their unresolved actionable content still blocks the merge; missing commit_id alone is not uncertainty. If identity, timing, or status cannot otherwise be established, stop and report the uncertainty instead of guessing. After any fix and push, restart this gate from the new head SHA.