From 99226ded1f27d8c39e453ed0e6697322af4db763 Mon Sep 17 00:00:00 2001 From: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> Date: Fri, 6 Mar 2026 15:04:55 +0000 Subject: [PATCH] fix(skill): add multi-line suggestion range minimization guidance The review bot posted a suggestion on PR #1309 with start_line covering correct code (the git-wt elseif branch) along with the duplicate else block. Applying it would have removed a legitimate fallback path. Add explicit guidance to verify that every line in a multi-line suggestion range actually needs changing before posting. Closes #1310 Co-Authored-By: Claude Opus 4.6 --- .claude/skills/review-pr/SKILL.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.claude/skills/review-pr/SKILL.md b/.claude/skills/review-pr/SKILL.md index a27201de82..c0610004aa 100644 --- a/.claude/skills/review-pr/SKILL.md +++ b/.claude/skills/review-pr/SKILL.md @@ -328,6 +328,10 @@ description: new text here - Prose-only comments are for changes too large or uncertain for a direct suggestion. - Multi-line suggestions: set `start_line` and `line` to define the range. + **Minimize the range** — only include lines that actually need changing. A + range that's too wide can delete correct code adjacent to the bug. Before + posting, verify that every line in [`start_line`, `line`] is either removed + or rewritten in the suggestion body. ### 5. Monitor CI