nearform/lastlight-flue/pr-comment

PR Comment

A maintainer @mentioned the bot on a PR with a question (not a request to write code, and not "review this"). The question is the entire job — answer it with evidence, in one comment. Examples: "does this consider X?", "why did we change Y?", "is the new function thread-safe?", "regression risk for existing callers?".

For general issue questions use issue-comment; for a full review use pr-review.

Procedure

1. Read the PR and the question

• github_get_pull_request → title, body, base, head.
• The triggering question is in context.commentBody. Answer that question —

don't generalise to a review or answer a different one.

2. Investigate with the diff in hand

Get the diff and read the code needed to answer well — a real answer about thread-safety or regression risk needs the surrounding code, not just the hunk.

• Cap: 8 file reads per invocation.
• "Does it consider X?" → also check whether tests in the diff cover X.
• "Regression risk?" → find callers of any function whose signature/behaviour

changed (github_search_code).

• Don't clone the repo unless a single answer genuinely needs cross-file traces

no MCP tool can give — most don't. If it truly needs a full audit, say so and recommend @last-light (which routes to pr-review) rather than blowing the cap.

3. Reply with one comment

github_add_issue_comment (PRs accept issue comments here). Keep it tight:

• Lead with the answer — yes / no / it depends. Don't bury it.
• Cite `path:line` — clickable in the GitHub UI.
• 3–8 sentences or a short bulleted list. No headings.
• If it's unanswerable from the PR alone, say so and name the specific

information you'd need.

Yes — src/foo.ts:42 checks X before calling bar(), and

tests/foo.test.ts:118 asserts the rejection path. The only place X isn't

validated is the legacy barLegacy (src/foo.ts:67), which this PR doesn't

touch — worth a separate issue if you want it covered.

Do not

• Post a formal review (github_create_pull_request_review) — that's

pr-review's job and would collide with its blocking check.

• Modify code, push, or add labels. One comment, nothing else.
• Answer a tangent you noticed — note it in at most one trailing sentence.

Tool usage

GitHub operations via github_* MCP tools only — never gh CLI, curl, or raw HTTP.