feat(examples): separate staleness check from agent via github-script

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 GitHub Action 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,38 @@
 description = "Analyzes and cleans up older issues by checking code validity, duplicates, and providing a triage summary."
 prompt = """
-## 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.
 
 ## 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`
+2. **EFFICIENCY**: If the issue is too vague, close it immediately and stop. Do not investigate code for vague issues.
 
 ## Task Lifecycle
 
-### 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}`
-    - STOP execution.
-- If not stale or vague, proceed to Step 2.
+### Step 1: Setup & Vagueness Check
+- 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:
+  - 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.
 
 ### 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.
+- 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." --repo !{echo $REPOSITORY}`
+  - **STOP EXECUTION IMMEDIATELY**.
 
 ### 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.
+- Search for duplicates using `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 IMMEDIATELY**.
 
 ### Step 4: Triage Summary
 - If unique and valid, provide a summary comment using these instructions:
 ```
 !{echo $CUSTOM_INSTRUCTIONS}
 ```
 - Action: `gh issue comment !{echo $ISSUE_NUMBER} --body "### Triage Summary\n\n<your summary>" --repo !{echo $REPOSITORY}`
-- STOP.
+- **STOP EXECUTION**.
 """

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

@@ -61,10 +61,67 @@ jobs:
       id-token: 'write'
       issues: 'write'
     steps:
+      - name: 'Check for Staleness'
+        id: 'staleness'
+        uses: 'actions/github-script@v7'
+        env:
+          ISSUE_NUMBER: '${{ matrix.issue_number }}'
+        with:
+          script: |-
+            const issueNumber = parseInt(process.env.ISSUE_NUMBER, 10);
+            console.log(`Checking staleness for issue #${issueNumber}`);
+
+            const { data: issue } = await github.rest.issues.get({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: issueNumber,
+            });
+            const reporter = issue.user.login;
+
+            const { data: comments } = await github.rest.issues.listComments({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: issueNumber,
+            });
+
+            // Find last maintainer comment
+            const maintainerComments = comments.filter(c => c.user.login !== reporter && !c.user.login.includes('github-actions') && c.user.type !== 'Bot');
+
+            if (maintainerComments.length > 0) {
+              const lastMaintainerComment = maintainerComments[maintainerComments.length - 1];
+              const reporterReplied = comments.some(c => c.user.login === reporter && new Date(c.created_at) > new Date(lastMaintainerComment.created_at));
+              
+              if (!reporterReplied) {
+                const daysAgo = (new Date() - new Date(lastMaintainerComment.created_at)) / (1000 * 60 * 60 * 24);
+                console.log(`Last maintainer comment was ${daysAgo.toFixed(1)} days ago.`);
+                
+                if (daysAgo > 7) {
+                  console.log(`Issue is stale. Closing.`);
+                  await github.rest.issues.createComment({
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    issue_number: issueNumber,
+                    body: "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."
+                  });
+                  await github.rest.issues.update({
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    issue_number: issueNumber,
+                    state: 'closed'
+                  });
+                  core.setOutput('is_stale', 'true');
+                  return;
+                }
+              }
+            }
+            core.setOutput('is_stale', 'false');
+
       - name: 'Checkout Current Repository'
+        if: steps.staleness.outputs.is_stale != 'true'
         uses: 'actions/checkout@v4'
 
       - name: 'Run Gemini Issue Cleanup'
+        if: steps.staleness.outputs.is_stale != 'true'
         uses: 'google-github-actions/run-gemini-cli@v0' # Replace with actual version when deploying
         env:
           ISSUE_NUMBER: '${{ matrix.issue_number }}'