Skip to content

fix(review-pr): always leave a final verdict when no issues found - #98

Open
grushikhin wants to merge 1 commit into
masterfrom
fix/review-pr-final-verdict-when-clean
Open

fix(review-pr): always leave a final verdict when no issues found#98
grushikhin wants to merge 1 commit into
masterfrom
fix/review-pr-final-verdict-when-clean

Conversation

@grushikhin

Copy link
Copy Markdown

Problem

The /review-pr skill runs via claude-code-action with track_progress: true + use_sticky_comment: true (see devops/.github/actions/agent-review). When a PR is clean, the skill said:

If you found no issues → Do not post any comments. Simply report to the user that no issues were found.

So the reviewer posted nothing, and the sticky progress comment stayed stuck on the interim "I'll analyze this and get back to you" placeholder. Reviewers/authors saw a finished-but-empty comment and couldn't tell the PR was actually reviewed and clean.

Observed on cloudbankin-data-export PR #258 (dev→master): review ran all 6 agents, No buffered inline comments, but the sticky comment never got a verdict.

Fix

Change the "no issues" instruction: still no inline comments, but always end with a short final verdict in the sticky comment (e.g. ✅ Reviewed — no issues found.), clarified as the tracking/sticky comment rather than a separate overall review report (so it doesn't conflict with the "inline comments only" rule).

Scope: only review-pr (it posts to the PR). review-local-changes is unchanged — it reports locally and has no sticky comment.

The review posts via claude-code-action with track_progress + sticky
comment. The 'no issues -> do not post any comments' instruction left the
sticky comment stuck on the interim 'I'll analyze this and get back to
you' placeholder, so clean PRs showed no visible result. Instruct the
reviewer to finish with a short verdict (e.g. 'Reviewed — no issues
found') in the sticky comment, clarified as the tracking comment (not a
separate review report).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant