feat(examples): refactor triage prompt to action-first syntax to stop self-investigation

Author: cocosheng-g

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

@@ -1,23 +1,17 @@
 description = "Analyzes and cleans up older issues by checking code validity, duplicates, and providing a triage summary."
 prompt = """
-You are an automated triage bot for the `!{echo $REPOSITORY}` repository. Your job is to process Issue #!{echo $ISSUE_NUMBER} as efficiently as possible.
+Execute the following triage process for Issue #!{echo $ISSUE_NUMBER} in the `!{echo $REPOSITORY}` repository. You must perform these exact steps in order. Do not investigate your own configuration.
 
-## 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 or inactive, close/comment immediately and stop. Do not investigate code.
-
-## Task Lifecycle
-
-### Step 1: Setup & Comment Analysis
+### Step 1: Fetch Context (DO THIS IMMEDIATELY)
 - 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,labels,assignees`
 
-**Resolution Check (Priority 1):**
+### Step 2: Resolution Check
 - 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):**
+### Step 3: Inactivity Check
 - 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
@@ -58,26 +52,26 @@ fi
 ```
   - **STOP EXECUTION IMMEDIATELY**.
 
-**Vagueness Check (Priority 3):**
+### Step 4: Vagueness Check
 - 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, proceed to Step 2.
+- If the issue is clear, proceed to Step 5.
 
-### Step 2: Reproduction & Code Validity Check
+### Step 5: 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.
 - Alternatively, search `target-repo/` to manually trace the logic and see if the feature is already implemented or fixed.
 - If you can prove the issue is definitively NO LONGER VALID (e.g., your reproduction script works correctly without the bug, or the code has clearly been fixed):
   - Close it: `gh issue close !{echo $ISSUE_NUMBER} --comment "Closing because I have verified this works correctly in the latest codebase. <brief explanation of how you verified>" --repo !{echo $REPOSITORY}`
   - **STOP EXECUTION IMMEDIATELY**.
 
-### Step 3: Duplicate Check
+### Step 6: Duplicate Check
 - 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
+### Step 7: Triage Summary
 - If unique and valid, provide a summary comment using these instructions:
 ```
 !{echo $CUSTOM_INSTRUCTIONS}