/fs-review on a merged PR gives no feedback

[mysticgohan1]

Body should be a bug report explaining: when you comment /fs-review on a PR that has already been merged or closed, nothing visible happens — no comment, no reaction emoji, no explanation. The review agent silently exits in post-review.sh (lines 33-37) with just a log message to Actions. The user has no way to know this was intentional. Expected behavior: post a brief comment on the PR explaining the review was skipped because the PR is already merged/closed. The pre-code.sh script already follows this pattern for /fs-code — it posts a visible comment when skipping. Steps to reproduce: merge any PR, then comment /fs-review on it.

[mysticgohan1]

/fs-triage

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 6:43 AM UTC · Completed 6:45 AM UTC
Commit: bb5c185 · View workflow run →

[fullsend-ai-triage]

Thanks for filing this. The description says post-review.sh silently exits at lines 33–37 with only a log message to Actions, but inspecting the current code at those lines shows it already posts a visible comment ("Review skipped — this PR is already merged/closed") before exiting.

Could you confirm whether you actually tested /fs-review on a merged PR and received no comment, or whether the issue was filed based on reading the code? If you did test it and no comment appeared, that would suggest the gh issue comment call on line 44 is failing silently (it uses 2>/dev/null || true, which swallows errors). Knowing whether the problem was observed in practice vs. inferred from code would significantly change the triage direction.

---

Labels: Issue reports a bug in the dispatch/review workflow scripts; type/bug and component/dispatch apply.

[guyoron1]

/fs-code

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 6:57 AM UTC · Completed 6:59 AM UTC
Commit: bb5c185 · View workflow run →