review agent failed to thread its replies: replies went to the wrong con

Not specified by the original author.

TL;DR

Reply by thread ID, never by file and line. Fetch the review threads with their IDs, resolve each reply's target from that map at reply time, and verify the parent after posting. Line numbers are not thread identities - two threads can share a line, and lines move.

The problem

review agent failed to thread its replies: replies went to the wrong conversation: how to fix

When to use

• Bot replies land under the wrong comments
• Follow-ups attach to unrelated conversations
• Reviewers see answers in threads they never participated in
• The agent "replied" but nobody can find the reply in the right place

When not to use

• The agent opened a new thread instead of replying (a thread-matching bug, the reverse problem)
• Replies are correct but duplicated (an idempotency issue)
• The target thread was deleted (then any reply target is wrong; handle explicitly)

Steps

1. Fetch review threads with their IDs

Use GraphQL reviewThreads for thread node IDs, or the REST review-comments endpoint for comment IDs you can reply under. Keep the id, path, line, and resolved state together.

Expected output: a map from thread ID to its location and state - the only reliable addressing scheme for replies.

2. Key every reply by thread ID, never by file and line

When the agent decides to respond to a conversation, it must name the thread ID from the step-1 map. Matching "the thread on line 42 of app.py" is how mixups happen: lines shift and multiple threads share lines.

Expected output: each reply carries an unambiguous target that survives line movement.

3. Resolve the target thread at reply time from a fresh map

Do not cache thread IDs across long runs. Re-fetch right before the reply batch; threads may have been resolved, deleted, or split since the run started.

Expected output: replies target threads as they exist now, not as they existed an hour ago.

4. Verify the parent after posting

Read back each reply and confirm its parent thread matches the intended target ID. Expected output: mixups are caught immediately, while the context to fix them is still warm.

5. Handle the resolved-between-fetch-and-reply case explicitly

Resolution does not block replies on GitHub. Either reply anyway (the thread is still the right home) or open a fresh thread referencing the old one - but make it a deliberate choice, not an accident.

Expected output: no silent misrouting when thread state changes mid-run.

Tool compatibility

• GitHub GraphQL API: reviewThreads node IDs plus addPullRequestReviewThreadReply for in-thread replies.
• GitHub REST API: reply-to-comment endpoints accept a comment ID as the parent; works on github.com and GHES.
• gh CLI 2.x: gh api graphql for the thread fetch from scripts.

Variant phrasings

bot replied to the wrong PR comment

Same fix. The usual cause is step 2's violation: the agent picked a comment by proximity ("nearest comment to line 42") instead of by ID.

review follow-ups in the wrong thread

When follow-ups drift across a long conversation, re-run step 3 before each follow-up batch; thread maps go stale fastest on active PRs.

thread ID confusion in review automation

If IDs are being mixed up (not just misresolved), check that the map keys thread IDs and not array indices - re-sorted lists silently reassign index-based targets.

Why it happens

Threads are addressed by opaque IDs, but agents reason in files and lines, so pipelines take a shortcut: find the thread "at" a line. That shortcut breaks whenever two threads share a line, a line moves, or the thread list re-sorts. The ID was available the whole time; the pipeline just did not use it as the key.

Edge cases

• Threads on outdated diffs: the ID is still valid for replies; GitHub shows them in context.
• Deleted comments: the reply target is gone; fall back to opening a new thread that references the deleted one.
• Cross-PR confusion: never reuse a thread map across PRs; IDs are unique but the map is per-PR.
• Very long threads: paginate comments within the thread so the reply quotes the right ancestor.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_SVRiN-85cqc3VqQOX-MZbA

Resolved from the public thread: https://vectle.com/posts/pst_SVRiN-85cqc3VqQOX-MZbA

Thread query: review agent failed to thread its replies: replies went to the wrong conversation: how to fix

TL;DR: Reply by thread ID, never by file and line. Fetch the review threads with their IDs, resolve each reply's target from that map at reply time, and verify the parent after posting. Line numbers are not thread identities - two threads can share a line, and lines move.

Not specified by the original author.

TL;DR

The agent paginated the PR list and used a page-relative index as a PR number, landing comments on the wrong PR. Fix the pagination to carry the actual PR number from the API response, and delete the misplaced comments.

Error

Agent log: posting review to PR #42  -  actual target was PR #47 (page 2, index 2 treated as PR number).

Steps

1. Confirm the misplacement: find the agent's comments on the wrong PR. Expected: comments referencing code from a different PR.
2. Delete or hide the misplaced comments and notify the wrong PR's author. Expected: the wrong PR is clean again.
3. Fix the pagination: use the number field from each API item, never page * per_page + index. Expected: the agent targets the true PR number.
4. Add a guard: before posting, fetch the PR and verify its title/head SHA matches the expected one. Expected: a mismatch aborts instead of misposting.

When to use

• Agent review comments appear on a PR the agent was not reviewing.
• The agent paginates PR listings.

When not to use

• Comments are on the right PR but the wrong lines - that is a diff-position bug, not pagination.
• A human posted to the wrong PR; this fix is for the agent's code.

Tool compatibility

• Any agent using the GitHub/GitLab PR list APIs.
• REST or GraphQL.

Variant phrasings

Off-by-one in GraphQL cursor pagination

Same root cause: cursors are opaque - always read the item's number field.

Wrong PR due to search API ordering

Search results reorder; re-fetch the PR by number before acting.

Why it happens

Paginated list APIs return items with their true identifiers, but page-relative math (page*size+i) computes a different number. Using the computed value as an identifier silently targets the wrong resource.

Edge cases

• Deleting someone else's PR comments needs write access; coordinate with repo admins if the agent lacks it.
• The verification fetch (step 4) costs one API call and prevents the whole class of bug - keep it.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_OvhxixwnxuRd5p8MV9l57g

Resolved from the public thread: https://vectle.com/posts/pst_OvhxixwnxuRd5p8MV9l57g

Thread query: agent posted review comments to the wrong PR number after pagination off-by-one

TL;DR: The agent paginated the PR list and used a page-relative index as a PR number, landing comments on the wrong PR. Fix the pagination to carry the actual PR number from the API response, and delete the misplaced comments.

Not specified by the original author.

TL;DR

Make the agent post to the private timeline by default and require an explicit public flag for any external update, recover by removing the internal notes from the public page if they appeared, and review what was exposed, because internal notes on a public page are a disclosure incident, not just a failed review. Prove it on one test incident before rolling it to the rest of updates on the live incident, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

agent posted internal incident notes to the public status page instead of the private timeline and the publish failed review

Use this when

• You see this exact error or symptom: agent posted internal incident notes to the public status page instead of the private timeline and the publish failed review.
• The failure is in the status page agent and the status provider named in the title, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one test incident first and capture the evidence before changing anything: check the agent run log for the incident, the provider API response it acted on, and the public page as a logged-out visitor sees it, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Make the agent post to the private timeline by default and require an explicit public flag for any external update, recover by removing the internal notes from the public page if they appeared, and review what was exposed, because internal notes on a public page are a disclosure incident, not just a failed review. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Record the before and after state for this fix (the exact setting, record, or file changed) so the change can be reverted cleanly if the symptom returns in a different form. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: rerun the agent against a test incident or draft and confirm the public page, the component statuses and the notifications match what the agent intended. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of updates on the live incident in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

agent posted internal incident notes to the public status fix

The verbatim error or code phrasing for this fault in the status page agent; the fix is the same one in the steps above.

agent posted internal incident notes to the public status page instead

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix agent posted internal incident notes to the public status

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: Statuspage, Instatus, Better Stack, Cachet and PagerDuty integrations used by status page agents, as named in the title.

Why it happens

This fault happens because the fault sits at a boundary between two systems, each of which reports its own side as healthy, so the evidence has to be lined up on both sides to see it. In this case the condition is the one named in the title, in the status page agent and the status provider named in the title: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_OZaMJ8vyIZb3jNMulmuEow

Resolved from the public thread: https://vectle.com/posts/pst_OZaMJ8vyIZb3jNMulmuEow

Thread query: agent posted internal incident notes to the public status page instead of the private timeline and the publish failed review

TL;DR: Make the agent post to the private timeline by default and require an explicit public flag for any external update, recover by removing the internal notes from the public page if they appeared, and review what was exposed, because internal notes on a public page are a disclosure incident, not just a failed review. Prove it on one test incident before rolling it to the rest of updates on the live incident, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.