Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
grushikhin wants to merge 1 commit into
base: master
Choose a base branch
from
+9 −1
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion plugins/review/skills/review-pr/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -276,7 +276,15 @@ When using `gh api repos/{owner}/{repo}/pulls/{pr_number}/comments`, post just o

#### If you found no issues

Do not post any comments. Simply report to the user that no issues were found.
Do not post inline review comments. But you MUST still end with a clear final
verdict in the sticky progress comment — never leave it on the interim
"I'll analyze this and get back to you" placeholder. Finish with a short line
such as:
Comment on lines +279 to +282

@LeoVS09 LeoVS09 Aug 6, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It caused not because of skill issue, it is bug within of claude code action, that closes claude code process once it launch the subagents


> ✅ Reviewed — no issues found.

This is the tracking/sticky comment, not a separate overall review report, so it
does not violate the "inline comments only" rule above.

## Remember

Expand Down