fix(review): always re-trigger Greptile after replying to comments (#643)

The /review skill was too conservative about re-triggering — it skipped
the @greptileai call when emoji reactions weren't found, causing missed
re-triggers on three separate PRs. Now defaults to always re-trigger,
with a single exception for when Greptile already thumbs-upped the reply.

Author: carlos-alm

.claude/skills/review/SKILL.md

@@ -201,60 +201,23 @@ After addressing all comments for a PR:
 
 ### 2g. Re-trigger reviewers
 
-**Greptile:** Only re-trigger if Greptile has outstanding concerns that you addressed. Before posting `@greptileai`, run these checks — if any says "skip", do NOT re-trigger:
+**Greptile:** Always re-trigger after replying to Greptile comments — whether the comment was actionable or not. The **only** exception is if Greptile already reacted to your most recent reply with a positive emoji (thumbs up, check, etc.), which means it is already satisfied.
 
-1. **Check if the last `@greptileai` trigger was already approved.** Find the most recent `@greptileai` comment (from anyone), then check if Greptile reacted to it with a thumbsup (+1). If it did, check whether Greptile posted any new inline review comments *after* that reaction. If thumbsup exists AND no new inline comments AND more than 15 minutes have passed since the trigger — Greptile approved. **Skip re-triggering.**
-
-   ```bash
-   # Count prior @greptileai trigger comments (excluding Greptile's own responses)
-   trigger_count=$(gh api repos/optave/codegraph/issues/<number>/comments --paginate \
-     --jq '[.[] | select(.body | test("@greptileai")) | select(.user.login != "greptile-apps[bot]")] | length')
-
-   if [ "$trigger_count" -eq 0 ]; then
-     # No prior trigger exists — first-ever run. Skip approval check AND check 2.
-     # Trigger Greptile for the first time (there are no prior comments to "respond to").
-     echo "No prior @greptileai trigger found. Triggering Greptile for the first time."
-     gh api repos/optave/codegraph/issues/<number>/comments -f body="@greptileai"
-     # After posting, proceed to step 2h (wait and re-check).
-   else
-     # Find the last @greptileai trigger comment (excluding Greptile's own responses)
-     trigger_comment=$(gh api repos/optave/codegraph/issues/<number>/comments --paginate \
-       --jq '[.[] | select(.body | test("@greptileai")) | select(.user.login != "greptile-apps[bot]")] | last | {id: .id, created_at: .created_at}')
-     trigger_id=$(echo "$trigger_comment" | jq -r '.id')
-     trigger_time=$(echo "$trigger_comment" | jq -r '.created_at')
-
-     # Check if greptile-apps[bot] thumbsupped the trigger comment
-     thumbsup_count=$(gh api repos/optave/codegraph/issues/comments/$trigger_id/reactions \
-       --jq '[.[] | select(.user.login == "greptile-apps[bot]" and .content == "+1")] | length')
-
-     # Count Greptile inline comments created after the trigger
-     inline_count=$(gh api repos/optave/codegraph/pulls/<number>/comments --paginate \
-       --jq "[.[] | select(.user.login == \"greptile-apps[bot]\" and .created_at > \"$trigger_time\")] | length")
-
-     # Compute elapsed minutes since the trigger
-     trigger_epoch=$(python3 -c "from datetime import datetime; print(int(datetime.fromisoformat('$trigger_time'.replace('Z','+00:00')).timestamp()))")
-     now_epoch=$(date -u +%s)
-     elapsed_minutes=$(( (now_epoch - trigger_epoch) / 60 ))
-     echo "Minutes since trigger: $elapsed_minutes"
-   fi
-   ```
-
-   **Decision logic:**
-   - Thumbsup exists AND no new inline comments AND >15 min since trigger → **Greptile approved. Skip re-triggering.**
-   - Thumbsup exists AND new inline comments exist → **Treat inline comments as outstanding concerns. Address them (step 2e), then re-trigger.** (Greptile sometimes thumbsups but still leaves nit comments.)
-   - Thumbsup exists AND no new inline comments AND <15 min since trigger → **Greptile is still processing. Wait until 15 min have passed**, then re-check. Do NOT post another `@greptileai`.
-   - No thumbsup AND <15 min since trigger → **Greptile hasn't responded yet. Wait until 15 min have passed**, then re-check.
-   - No thumbsup AND >15 min AND new inline comments exist → **Greptile has concerns. Address them (step 2e), then re-trigger.**
-   - No thumbsup AND >15 min AND no new inline comments → **Greptile never responded. Re-trigger once** (it may have missed the notification).
-
-2. **Check if you actually addressed any Greptile feedback.** If you made no code changes in response to Greptile comments (e.g., you only fixed CI or Claude comments), there's nothing new for Greptile to review — **skip re-triggering.**
-
-3. **Only if both checks above indicate outstanding concerns**, re-trigger:
-
-   ```bash
-   gh api repos/optave/codegraph/issues/<number>/comments \
-     -f body="@greptileai"
-   ```
+```bash
+# Step 1: Check if greptileai left a positive reaction on your most recent reply
+last_reply_id=$(gh api repos/optave/codegraph/issues/<number>/comments --paginate \
+  --jq '[.[] | select(.user.login != "greptile-apps[bot]")] | last | .id')
+
+positive_count=$(gh api repos/optave/codegraph/issues/comments/$last_reply_id/reactions \
+  --jq '[.[] | select(.user.login == "greptile-apps[bot]" and (.content == "+1" or .content == "hooray" or .content == "heart" or .content == "rocket"))] | length')
+
+# Step 2: If positive reaction exists → skip. Otherwise → re-trigger.
+if [ "$positive_count" -gt 0 ]; then
+  echo "Greptile already reacted positively — skipping re-trigger."
+else
+  gh api repos/optave/codegraph/issues/<number>/comments -f body="@greptileai"
+fi
+```
 
 **Claude (claude-code-review / claude bot):** Only re-trigger if you addressed something Claude specifically suggested. If you did:
 
@@ -313,7 +276,7 @@ If any subagent failed or returned an error, note it in the Status column as `ag
 - **Never force-push** unless fixing a commit message that fails commitlint. Amend + force-push is the only way to fix a pushed commit title (messages are part of the SHA). This is safe on feature branches. For all other problems, fix with a new commit.
 - **Address ALL comments from ALL reviewers** (Claude, Greptile, and humans), even minor/nit/optional ones. Leave zero unaddressed. Do not only respond to one reviewer and skip another.
 - **Always reply to comments** explaining what was done. Don't just fix silently. Every reviewer must see a reply on their feedback.
-- **Don't re-trigger Greptile if already approved.** If Greptile thumbsupped the last `@greptileai` trigger and posted no new inline comments, it's approved — skip re-triggering. If less than 15 minutes have passed since the last trigger, **wait** — do NOT post another `@greptileai`. Only re-trigger after confirming Greptile has outstanding concerns and you addressed them.
+- **Always re-trigger Greptile after replying.** Every time you reply to a Greptile comment — actionable or not — post `@greptileai` to re-trigger a review. The only exception: if Greptile already reacted to your reply with a positive emoji (thumbs up), skip the re-trigger.
 - **Only re-trigger Claude** if you addressed Claude's feedback specifically.
 - **No co-author lines** in commit messages.
 - **No Claude Code references** in commit messages or comments.