From 34f5a169a3f81f7953480d73052633b4aa670b4f Mon Sep 17 00:00:00 2001 From: Hauke Mehrtens Date: Sat, 11 Apr 2026 18:07:01 +0200 Subject: [PATCH] github: guide Claude to use inline comments and be concise Instruct Claude to prefer inline comments for file/line-specific findings and keep all feedback short and to the point. Co-Authored-By: Claude Sonnet 4.6 Link: https://github.com/openwrt/openwrt/pull/22897 Signed-off-by: Hauke Mehrtens --- .github/workflows/claude-code-review.yml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/.github/workflows/claude-code-review.yml b/.github/workflows/claude-code-review.yml index d53f085f225..757743d7e5e 100644 --- a/.github/workflows/claude-code-review.yml +++ b/.github/workflows/claude-code-review.yml @@ -34,3 +34,15 @@ jobs: claude_args: >- --allowedTools "mcp__github_inline_comment__create_inline_comment,Bash(grep:*)" --disallowedTools "Bash(git add:*),Bash(git commit:*),Bash(git rm:*),Bash(git push:*)" + env: + APPEND_SYSTEM_PROMPT: >- + IMPORTANT: For any issue tied to a specific file and line number, + you MUST call mcp__github_inline_comment__create_inline_comment to + post it as an inline comment on the diff. This is a separate + channel from mcp__github_comment__update_claude_comment and does + NOT violate the "only update your tracking comment" rule — both + tools should be used. Do NOT put line-specific issues in the + top-level tracking comment. Only use the top-level tracking + comment for a brief overall verdict. Never describe or summarize + what the PR does. Only report actual problems, concerns, or + suggestions. If nothing is wrong, say so in one short sentence.