feat(examples): allow custom instructions for issue cleanup triage summary

Author: cocosheng-g

examples/workflows/issue-cleanup/README.md

@@ -8,7 +8,7 @@ The Issue Cleanup workflow is designed to automate the triage of stale issues by
 
 1. **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.
 2. **Find Duplicates**: Checks if the issue has a more recent duplicate. If a duplicate exists, it closes the issue and links to the duplicate.
-3. **Summarize for Triage**: If an issue is still valid and unique, it provides a summary comment categorizing it as either `Maintainer-only` (epic, sensitive, internal) or `Help-wanted` (community-friendly).
+3. **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`).
 
 ## Usage
 

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

@@ -31,10 +31,10 @@ You MUST use your tools (like `grep_search`, `read_file`, and `run_shell_command
 
 ### Step 3: Provide Triage Summary
 - If the issue is still valid and NOT a duplicate, add a brief summary comment for further triaging.
-- State whether the issue should be categorized as:
-  - **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 !{echo $REPOSITORY}`
+- To formulate your summary, follow these custom instructions:
+```
+!{echo $CUSTOM_INSTRUCTIONS}
+```
+- Use `gh issue comment !{echo $ISSUE_NUMBER} --body "### Triage Summary\n\n<your summary based on custom instructions>" --repo !{echo $REPOSITORY}`
 - STOP execution. You are done with this issue.
 """

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

@@ -70,6 +70,7 @@ jobs:
           ISSUE_NUMBER: '${{ matrix.issue_number }}'
           REPOSITORY: '${{ github.repository }}'
           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:
           # Modify the auth settings depending on your environment
           gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}'