fix(examples): apply PR review suggestions for issue cleanup workflow

Author: cocosheng-g

examples/workflows/issue-cleanup/README.md

@@ -12,12 +12,10 @@ The Issue Cleanup workflow is designed to automate the triage of stale issues by
 
 ## Usage
 
-This example is tailored to process issues in a specific repository (`google-gemini/gemini-cli`) matching specific labels (`area/core`, `area/extensions`, `area/site`, `area/non-interactive`), selecting the 10 issues with the oldest last update time.
+This example is tailored to process issues in your repository matching specific labels (`area/core`, `area/extensions`, `area/site`, `area/non-interactive`), selecting the 10 issues with the oldest last update time.
 
 To adapt this to your own repository:
 
 1. Copy `gemini-issue-cleanup.yml` to your repository's `.github/workflows/` directory.
-2. Update the repository name and search string in the `Find old issues for cleanup` step in `gemini-issue-cleanup.yml`.
-3. Update the repository name in the `Checkout Target Repository Code` step in `gemini-issue-cleanup.yml`.
-4. Copy `gemini-issue-cleanup.toml` to your `.github/commands/` directory.
-5. Update the prompt instructions in `gemini-issue-cleanup.toml` replacing `google-gemini/gemini-cli` with your repository name.
+2. Update the search string in the `Find old issues for cleanup` step in `gemini-issue-cleanup.yml` to match your repository's labels.
+3. Copy `gemini-issue-cleanup.toml` to your `.github/commands/` directory.

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

@@ -1,32 +1,32 @@
 description = "Analyzes and cleans up older issues by checking code validity, duplicates, and providing a triage summary."
 prompt = """
 ## Role
-You are an expert AI triage assistant and repository maintainer for the `google-gemini/gemini-cli` repository.
+You are an expert AI triage assistant and repository maintainer for the `!{echo $REPOSITORY}` repository.
 
 ## Critical Constraints
 1. **Focus on the Target Issue**: DO NOT investigate the workflow files, `.github/commands/`, or how this tool is configured.
-2. **Clone the Target Repository**: Because this workflow runs independently, the target repository (`google-gemini/gemini-cli`) is NOT automatically present in the workspace. You MUST explicitly clone it (e.g., `git clone https://github.com/google-gemini/gemini-cli.git target-repo`) before beginning your investigation in Step 1.
+2. **Clone the Target Repository**: Because this workflow runs independently, the target repository (`!{echo $REPOSITORY}`) is NOT automatically present in the workspace. You MUST explicitly clone it (e.g., `git clone https://github.com/!{echo $REPOSITORY}.git target-repo`) before beginning your investigation in Step 1.
 3. **Efficiency**: Use your search tools (`grep_search`, `read_file`) quickly against the cloned repository. If you cannot definitively determine if an issue is still valid after a short investigation (e.g., within a few turns), proceed immediately to Step 2 and Step 3 (categorizing it as `Maintainer-only`). DO NOT spend excessive turns exploring the codebase.
 
 ## Task
-Your task is to analyze GitHub Issue #!{echo $ISSUE_NUMBER} in `google-gemini/gemini-cli` and sequentially perform three specific checks.
+Your task is to analyze GitHub Issue #!{echo $ISSUE_NUMBER} in `!{echo $REPOSITORY}` and sequentially perform three specific checks.
 You MUST use your tools (like `grep_search`, `read_file`, and `run_shell_command(gh)`) to investigate the codebase and issue tracker. Do NOT guess or hallucinate.
 
 ### Step 1: Check Code Validity
-- Use `gh issue view !{echo $ISSUE_NUMBER} --repo google-gemini/gemini-cli --json title,body,state,comments` to read the issue details.
+- Use `gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json title,body,state,comments` to read the issue details.
 - Search the local workspace to determine if the issue is still valid. 
   - For example, if it's a bug, does the buggy code still exist? If it's a feature request, has it already been implemented?
 - If you definitively determine the issue is NO LONGER VALID:
   - Close the issue and leave a brief comment explaining why (e.g., "Closing because this appears to have been fixed in the latest codebase. <explanation>").
-  - Use `gh issue close !{echo $ISSUE_NUMBER} --comment "Closing because this appears to have been fixed in the latest codebase. <explanation>" --repo google-gemini/gemini-cli`
+  - Use `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. You are done with this issue.
 
 ### Step 2: Check for Duplicates
 - If the issue is still valid, check if it's a duplicate of another issue that is already being tracked or worked on.
-- Use `gh issue list --search "<keywords>" --repo google-gemini/gemini-cli --state all` with relevant keywords to find potential duplicates.
+- Use `gh issue list --search "<keywords>" --repo !{echo $REPOSITORY} --state all` with relevant keywords to find potential duplicates.
 - If you find a clear duplicate that someone is working on or has already resolved:
   - Close the issue as not planned, pointing to the duplicate.
-  - Use `gh issue close !{echo $ISSUE_NUMBER} --reason "not planned" --comment "Closing as duplicate of #<duplicate_number>." --repo google-gemini/gemini-cli`
+  - Use `gh issue close !{echo $ISSUE_NUMBER} --reason "not planned" --comment "Closing as duplicate of #<duplicate_number>." --repo !{echo $REPOSITORY}`
   - STOP execution. You are done with this issue.
 
 ### Step 3: Provide Triage Summary
@@ -35,6 +35,6 @@ You MUST use your tools (like `grep_search`, `read_file`, and `run_shell_command
   - **Maintainer-only**: (e.g., epic, core architecture, sensitive fixes, internal tasks, or issues requiring deep investigation)
   - **Help-wanted**: (e.g., 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.
-- Use `gh issue comment !{echo $ISSUE_NUMBER} --body "### Triage Summary\n\n**Category:** <Maintainer-only OR Help-wanted>\n\n**Reasoning:** <brief explanation>" --repo google-gemini/gemini-cli`
+- Use `gh issue comment !{echo $ISSUE_NUMBER} --body "### Triage Summary\n\n**Category:** <Maintainer-only OR Help-wanted>\n\n**Reasoning:** <brief explanation>" --repo !{echo $REPOSITORY}`
 - STOP execution. You are done with this issue.
 """

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

@@ -25,18 +25,18 @@ jobs:
           GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN || github.token }}'
         run: |-
           echo '🔍 Finding old issues for cleanup...'
-          # Query matches target: google-gemini/gemini-cli, open issues, sorted by oldest last update time
+          # Query matches target repository, open issues, sorted by oldest last update time
           # with labels area/core, area/extensions, area/site, area/non-interactive
           ISSUES="$(gh issue list \
-            --repo google-gemini/gemini-cli \
+            --repo ${{ github.repository }} \
             --state 'open' \
             --search "label:area/core,area/extensions,area/site,area/non-interactive sort:updated-asc" \
             --json number \
             --limit 10 \
           )"
 
-          # Convert to JSON array of integers
-          ISSUE_NUMBERS="$(echo "${ISSUES}" | jq -c '[.[].number | tostring]')"
+          # Convert to JSON array
+          ISSUE_NUMBERS="$(echo "${ISSUES}" | jq -c '[.[].number]')"
 
           if [ "${ISSUE_NUMBERS}" = "[]" ] || [ -z "${ISSUE_NUMBERS}" ]; then
             echo "issue_numbers=[]" >> "${GITHUB_OUTPUT}"
@@ -68,6 +68,7 @@ jobs:
         uses: 'google-github-actions/run-gemini-cli@v0' # Replace with actual version when deploying
         env:
           ISSUE_NUMBER: '${{ matrix.issue_number }}'
+          REPOSITORY: '${{ github.repository }}'
           GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN || github.token }}'
         with:
           # Modify the auth settings depending on your environment