From bbdc4ca45be9dd259cd62e58cb4ad2a7d3ad0899 Mon Sep 17 00:00:00 2001 From: Wilko Date: Mon, 19 Oct 2026 13:04:32 +0200 Subject: [PATCH] Make the review bot post inline comments before its summary The inline comment server was set up, but the prompt only mentioned the tool at the very end as optional, so the bot never called it. It is now a required first step for to-dos that point to a changed line. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/claude-review.yml | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/.github/workflows/claude-review.yml b/.github/workflows/claude-review.yml index cc5142d..197bf08 100644 --- a/.github/workflows/claude-review.yml +++ b/.github/workflows/claude-review.yml @@ -87,7 +87,15 @@ jobs: Secondary: real bugs and security issues. Skip pure style nitpicks. - Output: post ONE top-level comment with `gh pr comment --body ...`. + Output, in this order: + 1. Inline comments FIRST: for each of the (at most 3) most important + to-dos that point to a changed line in the diff, call + `mcp__github_inline_comment__create_inline_comment` with + `confirmed: true`, the file path and the line number in the new + version of the file. One or two sentences each: what is wrong and + how to fix it. Skip this step only if no to-do points to a changed + line. + 2. Then post ONE top-level comment with `gh pr comment --body ...`. Write it for a busy maintainer and a contributor who may not be a native English speaker: short sentences, plain English, explain effects in terms @@ -135,10 +143,6 @@ jobs: small, low-risk to-dos remain; ❌ for breaking changes, unresolved compatibility risks or real bugs. - Inline comments: use `mcp__github_inline_comment__create_inline_comment` - (with `confirmed: true`) only for the at most 3 most important problems, - each in one or two sentences. - Be concrete. If unsure, say so instead of guessing. Only post GitHub comments; don't submit review text as messages. claude_args: |