feat(examples): let AI agent analyze comments to identify resolved issues before handling 30-day inactivity

Author: cocosheng-g

examples/workflows/issue-cleanup/gemini-issue-cleanup.toml

@@ -4,17 +4,65 @@ You are an automated triage bot for the `!{echo $REPOSITORY}` repository. Your j
 
 ## Critical Constraints
 1. **NO META-ANALYSIS**: DO NOT read local files in the repository you are running in (like `package.json`, `README.md`, or `.github/`). Only read files within the `target-repo/` folder you clone in Step 1.
-2. **EFFICIENCY**: If the issue is too vague, close it immediately and stop. Do not investigate code for vague issues.
+2. **EFFICIENCY**: If the issue is too vague or inactive, close/comment immediately and stop. Do not investigate code.
 
 ## Task Lifecycle
 
-### Step 1: Setup & Vagueness Check
+### Step 1: Setup & Comment Analysis
 - Run `git clone https://github.com/!{echo $REPOSITORY}.git target-repo`
-- Run `gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json title,body,author,comments`
-- **Vagueness Check**: If the issue description is fundamentally missing context (no logs, no repro steps, just "it's broken") AND no one has asked for more information yet:
+- Run `gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json title,body,author,comments,labels,assignees`
+
+**Resolution Check (Priority 1):**
+- Read the comments. Does the latest comment indicate that the issue has been fixed, resolved, or is functioning properly?
+  - If YES: `gh issue close !{echo $ISSUE_NUMBER} --comment "Closing because the latest comments indicate this issue has been resolved. Feel free to reopen if the problem persists." --reason "completed" --repo !{echo $REPOSITORY}`
+  - **STOP EXECUTION IMMEDIATELY**.
+
+**Inactivity Check (Priority 2):**
+- Is `!{echo $INACTIVE_OVER_30_DAYS}` equal to `true`?
+  - If YES (and it was not resolved above): Execute the following bash script exactly as written to handle the inactivity.
+```bash
+ISSUE_JSON=$(gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json author,labels,assignees)
+REPORTER=$(echo "$ISSUE_JSON" | jq -r '.author.login')
+HAS_ASSIGNEES=$(echo "$ISSUE_JSON" | jq '.assignees | length > 0')
+ASSIGNEE_MENTIONS=$(echo "$ISSUE_JSON" | jq -r '.assignees | map("@" + .login) | join(" ")')
+IS_HIGH_PRIORITY=$(echo "$ISSUE_JSON" | jq '.labels | map(.name | ascii_downcase) | any(. == "priority/p0" or . == "priority/p1" or . == "p0" or . == "p1")')
+IS_FEATURE=$(echo "$ISSUE_JSON" | jq '.labels | map(.name | ascii_downcase) | any(contains("feature") or contains("enhancement"))')
+
+gh issue edit !{echo $ISSUE_NUMBER} --remove-label "status/need-triage" --repo !{echo $REPOSITORY} 2>/dev/null || true
+gh issue edit !{echo $ISSUE_NUMBER} --add-label "status/needs-info" --repo !{echo $REPOSITORY} 2>/dev/null || true
+
+COMMENT=""
+if [ "$IS_FEATURE" = "true" ]; then
+  COMMENT="@${REPORTER}, this feature request hasn't been updated in over a month. Please reopen if this is still needed."
+else
+  COMMENT="@${REPORTER}, this issue hasn't been updated in over a month. Could you please try reproducing it with the latest build? If it still occurs, please provide detailed reproduction steps."
+fi
+
+if [ "$IS_HIGH_PRIORITY" = "false" ]; then
+  if [ "$HAS_ASSIGNEES" = "true" ]; then
+    COMMENT="${COMMENT}\n\n${ASSIGNEE_MENTIONS}, please reopen if you are actively working on this."
+  elif [ "$IS_FEATURE" = "false" ]; then
+    COMMENT="${COMMENT} Feel free to reopen this issue."
+  fi
+else
+  if [ "$HAS_ASSIGNEES" = "true" ]; then
+    COMMENT="${COMMENT}\n\n${ASSIGNEE_MENTIONS}, checking in on this high priority issue."
+  fi
+fi
+
+gh issue comment !{echo $ISSUE_NUMBER} --body "$COMMENT" --repo !{echo $REPOSITORY}
+
+if [ "$IS_HIGH_PRIORITY" = "false" ]; then
+  gh issue close !{echo $ISSUE_NUMBER} --reason "not planned" --repo !{echo $REPOSITORY}
+fi
+```
+  - **STOP EXECUTION IMMEDIATELY**.
+
+**Vagueness Check (Priority 3):**
+- If the issue is NOT inactive over 30 days: Is the issue description fundamentally missing context (no logs, no repro steps, just "it's broken") AND no one has asked for more information yet?
   - Ask the reporter: `gh issue comment !{echo $ISSUE_NUMBER} --body "@<reporter_username>, thank you for the report! Could you please provide more specific details (e.g., reproduction steps, expected behavior, and environment)? Closing this as vague if no response is received in a week." --repo !{echo $REPOSITORY}`
   - **STOP EXECUTION IMMEDIATELY**.
-- If the issue is clear or the reporter has provided info, proceed to Step 2.
+- If the issue is clear, proceed to Step 2.
 
 ### Step 2: Reproduction & Code Validity Check
 - If the issue describes a reproducible bug (e.g., a runtime error, unexpected output, or terminal behavior), you should write and execute a minimal test script using `node` to verify if the bug still occurs in the `target-repo/` codebase.

examples/workflows/issue-cleanup/gemini-issue-cleanup.yml

@@ -198,110 +198,12 @@ jobs:
             console.log(`Issue was last updated ${lastUpdateDaysAgo.toFixed(1)} days ago.`);
 
             if (lastUpdateDaysAgo > 30) {
-              // Check if the last comment says it's fixed
-              if (comments.length > 0) {
-                const lastCommentBody = comments[comments.length - 1].body.toLowerCase();
-                const resolvedKeywords = ['functioning properly', 'works now', 'is fixed', 'resolved now'];
-                if (resolvedKeywords.some(kw => lastCommentBody.includes(kw))) {
-                  console.log(`Issue appears resolved in the last comment. Closing.`);
-                  await github.rest.issues.createComment({
-                    owner: context.repo.owner,
-                    repo: context.repo.repo,
-                    issue_number: issueNumber,
-                    body: "Closing because the latest comments indicate this issue has been resolved. Feel free to reopen if the problem persists."
-                  });
-                  await github.rest.issues.update({
-                    owner: context.repo.owner,
-                    repo: context.repo.repo,
-                    issue_number: issueNumber,
-                    state: 'closed',
-                    state_reason: 'completed'
-                  });
-                  core.setOutput('is_stale', 'true');
-                  return;
-                }
-              }
-
-              console.log(`Issue has been inactive for over a month. Asking for repro.`);
-              
-              try {
-                await github.rest.issues.removeLabel({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  issue_number: issueNumber,
-                  name: 'status/need-triage'
-                });
-              } catch (e) {
-                // Ignore if label doesn't exist
-              }
-              
-              try {
-                await github.rest.issues.addLabels({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  issue_number: issueNumber,
-                  labels: ['status/needs-info']
-                });
-              } catch (e) {
-                console.log('Failed to add needs-info label:', e.message);
-              }
-              
-              const assignees = issue.assignees.map(a => a.login);
-              const hasAssignees = assignees.length > 0;
-              const assigneeMentions = hasAssignees ? assignees.map(a => `@${a}`).join(' ') : '';
-              
-              const isHighPriority = issue.labels.some(l => {
-                const name = typeof l === 'string' ? l : l.name;
-                const lowerName = name.toLowerCase();
-                return lowerName === 'priority/p0' || lowerName === 'priority/p1' || lowerName === 'p0' || lowerName === 'p1';
-              });
-
-              const isFeatureRequest = issue.labels.some(l => {
-                const name = typeof l === 'string' ? l : l.name;
-                const lowerName = name.toLowerCase();
-                return lowerName.includes('feature') || lowerName.includes('enhancement');
-              });
-
-              let commentBody = '';
-              if (isFeatureRequest) {
-                commentBody = `@${reporter}, this feature request hasn't been updated in over a month. Please reopen if this is still needed.`;
-              } else {
-                commentBody = `@${reporter}, this issue hasn't been updated in over a month. Could you please try reproducing it with the latest build? If it still occurs, please provide detailed reproduction steps.`;
-              }
-
-              if (!isHighPriority) {
-                if (hasAssignees) {
-                  commentBody += `\n\n${assigneeMentions}, please reopen if you are actively working on this.`;
-                } else if (!isFeatureRequest) {
-                  commentBody += ` Feel free to reopen this issue.`;
-                }
-              } else {
-                if (hasAssignees) {
-                  commentBody += `\n\n${assigneeMentions}, checking in on this high priority issue.`;
-                }
-              }
-
-              await github.rest.issues.createComment({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: issueNumber,
-                body: commentBody
-              });
-
-              if (!isHighPriority) {
-                await github.rest.issues.update({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  issue_number: issueNumber,
-                  state: 'closed',
-                  state_reason: 'not_planned'
-                });
-              }
-              
-              core.setOutput('is_stale', 'true');
+              core.setOutput('inactive_over_30_days', 'true');
+              core.setOutput('is_stale', 'false'); // Let AI handle it
               return;
             }
 
+            core.setOutput('inactive_over_30_days', 'false');
             core.setOutput('is_stale', 'false');
 
       - name: 'Checkout Current Repository'
@@ -314,6 +216,7 @@ jobs:
         env:
           ISSUE_NUMBER: '${{ matrix.issue_number }}'
           REPOSITORY: '${{ github.repository }}'
+          INACTIVE_OVER_30_DAYS: '${{ steps.staleness.outputs.inactive_over_30_days }}'
           GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN || github.token }}'
           CUSTOM_INSTRUCTIONS: 'State whether the issue should be categorized as **Maintainer-only** (epic, core architecture, sensitive fixes, internal tasks, or issues requiring deep investigation) or **Help-wanted** (good for community, general bugs, features, or tasks ready for external help). Your comment should be brief and clearly explain *why* it fits that category.'
         with: