ci: Dynamically resolve bot fork repo to prevent push failures

- Fixes repository not found errors when pushing the fix branch in the issue-fix workflow by query-inspecting the authenticated bot's username and ensuring the fork exists via gh repo fork.
- Also updates the adk-issue-analyze skill output template to use a details tag for collapsible section and restructure questions.

Change-Id: If87b4ddbe897b9338aa6ee78221709e8777b0045

Author: boyangsvl

.agents/skills/adk-issue-analyze/SKILL.md

@@ -25,25 +25,24 @@ This skill provides a structured workflow for analyzing, verifying, and triaging
 ---
 
 ## Step 2: Deep Investigation & Analysis
-Address the following four critical questions and present your findings in a structured, premium report.
+Address the following three critical questions and present your findings in a structured, premium report.
 
 ### 1. What is broken?
 Explain the root cause of the issue or failure:
-- **Trace the execution flow**: Identify which components, classes, or functions are malfunctioning.
-- **Pinpoint the bug**: Detail why the system is behaving incorrectly and where the failure originates (e.g. incorrect logic, missing configuration, unhandled states).
-
-### 2. Is the issue legitimate?
-Inspect the codebase to confirm if the issue represents a real problem:
-- **Examine the description**: Identify the component, class, function, or file referenced.
-- **Search the codebase**: Use `grep_search` to locate the relevant files/functions in the local workspace.
-- **Inspect the code**: Open the files using `view_file` to analyze the code's current logic.
-- **Verify the bug**:
-  - Is the reported problem actually present in the code?
-  - Does it produce the reported error or behavior under the current version (ADK 2.0)?
-  - Is it a documentation typo, setup discrepancy, or a genuine code/logic bug?
-- **Document your code evidence**: Reference specific file paths and line ranges (using clickable markdown file links, e.g., `[skill_toolset.py](file:///path/to/file#L123)`) in your report.
-
-### 3. Should we fix it?
+- **Trace the execution flow**: Use `grep_search` and `view_file` to locate and analyze the malfunctioning components, classes, or functions in the local workspace.
+- **Pinpoint the bug**: Detail why the system is behaving incorrectly and where the failure originates (e.g., incorrect logic, missing configuration, unhandled states).
+- **Document code evidence**: Reference specific file paths and line ranges using clickable markdown file links, e.g., `[filename.py](file:///absolute/path/to/file#L100-L120)`.
+
+### 2. Is there a linked PR that fixes this issue?
+Search for any existing pull requests that attempt to resolve the issue:
+- **Search PRs**: Run `gh pr list --repo google/adk-python --search "<issue_number>"` to list pull requests mentioning the issue number in the branch name, title, or body.
+- **Verify the PR details**: If PRs are found, fetch their details:
+  ```bash
+  gh pr view <pr_number> --repo google/adk-python --json number,title,state,url,body,author
+  ```
+- **Analyze progress**: Check if the PR is open, merged, or closed, and if it successfully fixes the issue according to the repository's testing patterns.
+
+### 3. Recommendation
 Formulate a recommendation on whether the issue should be addressed:
 - **Assess the impact**:
   - Does it break core functionality?
@@ -55,16 +54,6 @@ Formulate a recommendation on whether the issue should be addressed:
 - **Evaluate workarounds**: Is there a clean workaround, or is a core fix necessary?
 - **Final Recommendation**: Clearly declare whether we should fix it, along with the reasoning and estimated complexity/scope of the fix.
 
-### 4. Is there a linked PR that fixes this issue?
-Search for any existing pull requests that attempt to resolve the issue:
-- **Search PRs**: Run `gh pr list --repo google/adk-python --search "<issue_number>"` to list pull requests mentioning the issue number in the branch name, title, or body.
-- **Verify the PR details**: If PRs are found, fetch their details:
-  ```bash
-  gh pr view <pr_number> --repo google/adk-python --json number,title,state,url,body,author
-  ```
-- **Analyze progress**: Check if the PR is open, merged, or closed, and if it successfully fixes the issue according to the repository's testing patterns.
-- **Present the structured report**: Format and present your findings structured as a premium report following the **Report Template** below.
-
 ---
 
 ## Report Template
@@ -74,36 +63,30 @@ Present your final analysis as a high-quality markdown response using the follow
 ```markdown
 # GitHub Issue #<issue_number> Analysis: <Issue Title>
 
-## Detailed Analysis
+## Executive Summary
+1. **What is broken?** [Brief explanation of the root cause or error]
+2. **Is there a linked PR that fixes this issue?** [None / Yes, PR #<pr_number> - <state>]
+3. **Recommendation**: [Should Fix (High Priority) / Should Fix (Medium/Low Priority) / Won't Fix / Needs Discussion - priority & brief reasoning]
+
+<details>
+<summary><b>Detailed Analysis</b></summary>
 
 ### 1. Root Cause Analysis ("What is broken?")
 - Explanation of the failure or bug (what is failing and why).
 - Pinpoint the exact file, function, or design component that is malfunctioning.
+- Code references: [filename.py](file:///absolute/path/to/file#L100-L120)
 
-### 2. Legitimacy Analysis
-- **Status**: [Legitimate Bug / Feature Request / Duplicate / Invalid / Not Reproducible]
-- **Evidence**:
-  - Code references: [filename.py](file:///absolute/path/to/file#L100-L120)
-  - Analysis of code behavior and why the issue occurs.
+### 2. Existing Pull Requests ("Is there a linked PR that fixes this issue?")
+- **Linked PR**: [None / Pull Request #<pr_number> - <PR Title> (<state>)]
+- **PR URL**: <PR URL>
+- **Analysis**: Brief summary of the PR's approach and status (e.g., "Fixes the bug by implementing X in Y, currently awaiting review").
 
-### 3. Fix Recommendation
+### 3. Recommendation
 - **Recommendation**: [Should Fix (High Priority) / Should Fix (Medium/Low Priority) / Won't Fix / Needs Discussion]
 - **Rationale**:
   - Impact on user experience, workflows, or architecture.
   - Implementation complexity and risk of side effects.
-
-### 4. Existing Pull Requests
-- **Linked PR**: [None / Pull Request #<pr_number> - <PR Title> (<state>)]
-- **PR URL**: <PR URL>
-- **Analysis**: Brief summary of the PR's approach and status (e.g., "Fixes the bug by implementing X in Y, currently awaiting review").
-
----
-
-## Executive Summary
-1. **What is broken?** [Brief explanation of the root cause or error]
-2. **Is the issue legitimate?** [Yes / No - brief explanation]
-3. **Should we fix it?** [Yes / No / Needs Discussion - priority & brief reasoning]
-4. **Is there a linked PR that fixes this issue?** [None / Yes, PR #<pr_number> - <state>]
+</details>
 ```
 
 ---

.github/workflows/issue-fix.yml

@@ -103,8 +103,15 @@ jobs:
             # Append the closes tag using Python to avoid relying on LLM formatting
             python -c "import os, subprocess; msg = subprocess.check_output(['git', 'log', '-1', '--pretty=%B'], text=True); tag = 'closes https://github.com/google/adk-python/issues/' + os.environ['ISSUE_NUMBER']; subprocess.run(['git', 'commit', '--amend', '-m', msg.strip() + '\n\n' + tag], check=True) if tag not in msg else None"
 
+            # Retrieve the username of the authenticated user
+            BOT_USER=$(gh api user --jq .login)
+            echo "Authenticated bot user is $BOT_USER"
+
+            # Ensure the fork exists
+            gh repo fork google/adk-python --clone=false --remote=false || true
+
             # Push the branch to the bot fork
-            git remote add fork https://x-access-token:${{ secrets.ADK_TRIAGE_AGENT }}@github.com/adk-bot/adk-python.git
+            git remote add fork "https://x-access-token:${{ secrets.ADK_TRIAGE_AGENT }}@github.com/${BOT_USER}/adk-python.git"
             git push fork "$BRANCH_NAME" --force
 
             # Retrieve the commit message of the last commit
@@ -115,7 +122,7 @@ jobs:
               --repo google/adk-python \
               --title "fix(issue): fix issue #${ISSUE_NUMBER}" \
               --body "$COMMIT_MSG" \
-              --head "adk-bot:$BRANCH_NAME" \
+              --head "${BOT_USER}:$BRANCH_NAME" \
               --base "main"
           else
             echo "No changes made by the agent. Skipping PR creation."