feat(examples): implement native staleness check to save AI resources

Author: cocosheng-g

examples/workflows/issue-cleanup/README.md

@@ -6,10 +6,11 @@ This document describes a workflow to batch-process and clean up older open issu
 
 The Issue Cleanup workflow is designed to automate the triage of stale issues by using the Gemini CLI to:
 
-1. **Check for Staleness and Vagueness**: Identifies issues with insufficient information. If a request for more information has gone unanswered for over a week, it closes the issue. If it's a new vague issue, it asks the reporter for specific details.
-2. **Check Code Validity**: Determines if an issue is still relevant against the current codebase. If the issue has already been resolved implicitly, it will close the issue with an explanation.
-3. **Find Duplicates**: Checks if the issue has a more recent duplicate. If a duplicate exists, it closes the issue and links to the duplicate.
-4. **Summarize for Triage**: If an issue is still valid and unique, it provides a summary comment based on customizable instructions (e.g., categorizing it as `Maintainer-only` or `Help-wanted`). If no custom instructions are provided, it falls back to a standard triage summary (identifying the core problem, impact, and next steps).
+1. **Check for Staleness (Native)**: Identifies if an issue has been waiting for reporter feedback for over 7 days. If so, it closes the issue directly via a native bash script to save AI resources.
+2. **Check for Vagueness (AI)**: If an issue is not stale but lacks sufficient information (e.g., reproduction steps), the agent asks the reporter for specific details and stops.
+3. **Check Code Validity (AI)**: Determines if an issue is still relevant against the current codebase. If the issue has already been resolved implicitly, it will close the issue with an explanation.
+4. **Find Duplicates (AI)**: Checks if the issue has a more recent duplicate. If a duplicate exists, it closes the issue and links to the duplicate.
+5. **Summarize for Triage (AI)**: If an issue is still valid and unique, it provides a summary comment based on customizable instructions (e.g., categorizing it as `Maintainer-only` or `Help-wanted`). If no custom instructions are provided, it falls back to a standard triage summary.
 
 ## Usage
 

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

@@ -1,39 +1,47 @@
 description = "Analyzes and cleans up older issues by checking code validity, duplicates, and providing a triage summary."
 prompt = """
+## Primary Directive
+You are an automated triage bot. Your ONLY purpose is to execute the issue triage task below for Issue #!{echo $ISSUE_NUMBER} in `!{echo $REPOSITORY}`.
+**DO NOT** investigate the current workspace, `.github/` folder, `package.json`, or any local documentation.
+**DO NOT** explain your plan or the workflow to the user.
+**MANDATORY FIRST ACTION**: You MUST immediately run `git clone https://github.com/!{echo $REPOSITORY}.git target-repo` and then proceed directly to Step 1.
+
 ## Role
-You are an automated triage bot for the `!{echo $REPOSITORY}` repository. Your job is to process Issue #!{echo $ISSUE_NUMBER} as efficiently as possible.
+You are an expert AI triage assistant for the `!{echo $REPOSITORY}` repository.
 
 ## 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. **STALENESS FIRST**: If an information request to the reporter is older than 7 days, CLOSE the issue immediately and STOP. Do not investigate the code.
-3. **MANDATORY SERIAL START**: In your very first turn, you MUST execute exactly these three tools:
-    - `git clone https://github.com/!{echo $REPOSITORY}.git target-repo`
-    - `gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json author,comments,updatedAt`
-    - `date`
+1. **No Workspace Meta-Analysis**: Do not read local files that are not part of the target repository you cloned.
+2. **Efficiency**: Use `grep_search` and `read_file` quickly. If you cannot definitively prove an issue is invalid within 5 turns, move to Step 3 and categorize as `Maintainer-only`.
+3. **Tool Usage**: Use `gh` for all GitHub interactions and `git` for cloning. Use `target-repo/` as the root for all code searches.
 
-## Task Lifecycle
+## Task
+Perform these checks for Issue #!{echo $ISSUE_NUMBER}:
 
-### Step 1: Staleness & Vagueness Check
-- Examine the `gh issue view` output.
-- **Vagueness**: If the issue is too vague (no logs, no repro steps), @mention the reporter asking for specific details. STOP.
-- **Staleness**: If a maintainer or bot previously asked for information and it has been more than 7 days (check against `date`) and the reporter has NOT replied:
-    - `gh issue close !{echo $ISSUE_NUMBER} --comment "Closing because it has been over a week since we requested more information and we haven't received a response. Feel free to reopen if you can provide the requested details." --repo !{echo $REPOSITORY}`
+### Step 1: Check for Vagueness
+- Use `gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json title,body,author,comments` to read the issue.
+- If the issue description is too vague to be actionable (e.g., missing reproduction steps, environment, or clear goal) 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.
-- If not stale or vague, proceed to Step 2.
+- If the issue is clear or the reporter has provided the requested info, proceed to Step 2.
 
-### Step 2: Code Validity Check
-- Search `target-repo/` to see if the bug still exists or the feature is already implemented.
-- If fixed: `gh issue close !{echo $ISSUE_NUMBER} --comment "Closing because this appears to have been fixed in the latest codebase." --repo !{echo $REPOSITORY}`. STOP.
+### Step 2: Check Code Validity
+- Search the `target-repo/` directory to see if the issue is still relevant.
+- If definitively NO LONGER VALID:
+  - Close it: `gh issue close !{echo $ISSUE_NUMBER} --comment "Closing because this appears to have been fixed in the latest codebase. <explanation>" --repo !{echo $REPOSITORY}`
+  - STOP execution.
 
-### Step 3: Duplicate Check
-- Search for duplicates using `gh issue list`. 
-- If found: `gh issue close !{echo $ISSUE_NUMBER} --reason "not planned" --comment "Closing as duplicate of #<duplicate_number>." --repo !{echo $REPOSITORY}`. STOP.
+### Step 3: Check for Duplicates
+- Search for duplicates: `gh issue list --search "<keywords>" --repo !{echo $REPOSITORY} --state all`
+- If a clear duplicate is found:
+  - Close it: `gh issue close !{echo $ISSUE_NUMBER} --reason "not planned" --comment "Closing as duplicate of #<duplicate_number>." --repo !{echo $REPOSITORY}`
+  - STOP execution.
 
-### Step 4: Triage Summary
-- If unique and valid, provide a summary comment using these instructions:
+### Step 4: Provide Triage Summary
+- If unique and valid, provide a summary comment based on these instructions:
 ```
 !{echo $CUSTOM_INSTRUCTIONS}
 ```
-- Action: `gh issue comment !{echo $ISSUE_NUMBER} --body "### Triage Summary\n\n<your summary>" --repo !{echo $REPOSITORY}`
-- STOP.
+- Fallback (if instructions empty): Provide a standard summary of problem, impact, and next steps.
+- Comment: `gh issue comment !{echo $ISSUE_NUMBER} --body "### Triage Summary\n\n<your summary>" --repo !{echo $REPOSITORY}`
+- STOP execution.
 """

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

@@ -64,7 +64,50 @@ jobs:
       - name: 'Checkout Current Repository'
         uses: 'actions/checkout@v4'
 
+      - name: 'Check for Staleness'
+        id: 'check_staleness'
+        env:
+          GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN || github.token }}'
+          ISSUE_NUMBER: '${{ matrix.issue_number }}'
+          REPOSITORY: '${{ github.repository }}'
+        run: |-
+          echo "=== GET ISSUE DATA ==="
+          ISSUE_JSON=$(gh issue view "${ISSUE_NUMBER}" --repo "${REPOSITORY}" --json author,comments)
+
+          REPORTER=$(echo "${ISSUE_JSON}" | jq -r '.author.login')
+          echo "Reporter is: ${REPORTER}"
+
+          # Find the last comment by someone other than the reporter
+          LAST_MAINTAINER_COMMENT_DATE=$(echo "${ISSUE_JSON}" | jq -r '
+            .comments | reverse | map(select(.author.login != "'"${REPORTER}"'" and .author.login != "github-actions" and .author.login != "app/github-actions")) | .[0]?.updatedAt // "null"
+          ')
+
+          if [ "${LAST_MAINTAINER_COMMENT_DATE}" != "null" ] && [ -n "${LAST_MAINTAINER_COMMENT_DATE}" ]; then
+            echo "Last maintainer comment date: ${LAST_MAINTAINER_COMMENT_DATE}"
+            
+            # Check if reporter replied AFTER this date
+            REPORTER_REPLIED=$(echo "${ISSUE_JSON}" | jq -r '
+              .comments | map(select(.author.login == "'"${REPORTER}"'" and .updatedAt > "'"${LAST_MAINTAINER_COMMENT_DATE}"'")) | length > 0
+            ')
+            
+            if [ "${REPORTER_REPLIED}" = "false" ]; then
+              # Calculate days ago
+              DAYS_AGO=$(( ($(date +%s) - $(date -d "${LAST_MAINTAINER_COMMENT_DATE}" +%s)) / 86400 ))
+              echo "It has been ${DAYS_AGO} days since maintainer asked for info."
+              
+              if [ "${DAYS_AGO}" -gt 7 ]; then
+                echo "=== STALE ISSUE DETECTED. CLOSING NOW. ==="
+                gh issue close "${ISSUE_NUMBER}" --comment "Closing because it has been over a week since we requested more information and we haven't received a response. Feel free to reopen if you can provide the requested details." --repo "${REPOSITORY}"
+                echo "continue_ai=false" >> "${GITHUB_OUTPUT}"
+                exit 0
+              fi
+            fi
+          fi
+
+          echo "continue_ai=true" >> "${GITHUB_OUTPUT}"
+
       - name: 'Run Gemini Issue Cleanup'
+        if: steps.check_staleness.outputs.continue_ai == 'true'
         uses: 'google-github-actions/run-gemini-cli@v0' # Replace with actual version when deploying
         env:
           ISSUE_NUMBER: '${{ matrix.issue_number }}'