From bde1695ad198e5f2d616645cd50f68f9157a4dd9 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 17 Jul 2026 15:30:52 +0000 Subject: [PATCH] review-pr skill: report only genuine findings in review comments Reviews should post findings-only review comments on the PR. Positive or confirmatory remarks about things that work as expected add noise without value, so a clean review now posts nothing instead of an explicit all-clear. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01TSp2HwEMrw3LLaiDHRdhJY --- .claude/skills/review-pr/SKILL.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/.claude/skills/review-pr/SKILL.md b/.claude/skills/review-pr/SKILL.md index 69d34ac..67c6b9f 100644 --- a/.claude/skills/review-pr/SKILL.md +++ b/.claude/skills/review-pr/SKILL.md @@ -35,7 +35,10 @@ conventions. - **Unnecessary dependencies**: flag any new third-party dependency beyond `gopkg.in/yaml.v3` and ask if it's really justified over hand-rolling (see `CLAUDE.md` dependency philosophy). -4. Post review comments (or a summary if inline commenting isn't available) - focused on concrete, actionable issues — don't nitpick style that a +4. Post the results as review comments on the PR (inline where possible, + otherwise a single review comment). Only report genuine findings — + concrete, actionable issues. Do not comment on things that are fine, + pass the checklist, or work as expected; positive remarks and + "looks good" filler add noise, not value. Don't nitpick style that a linter would already catch. -5. If everything checks out, say so explicitly rather than staying silent. +5. If the review produces no findings, do not post any comments.