ADK Issue Triage & Analysis (Read-Only)

This skill provides a structured workflow for analyzing, verifying, and triaging GitHub issues from the google/adk-python repository. When instructed to analyze/triage an issue, follow this read-only workflow.

[!IMPORTANT] Strict Read-Only Constraint: This skill is strictly read-only. You MUST NOT modify any code, create new branches, or write any implementation. Your role is only to analyze the issue and output the report. Do NOT use file creation or editing tools (e.g. write_to_file, replace_file_content, edit_file, etc.).

Strict Tooling Constraint: Do NOT use curl, wget, or any HTTP requests to fetch issue/PR content. You MUST parse/extract the issue number and use strictly the custom fetch_github_issue / fetch_github_pr python tools (or the gh command).

Step 1: Retrieve and Parse the Issue

1. Extract the issue number: Parse the number from the link or prompt (e.g., https://github.com/google/adk-python/issues/5882 -> 5882).
2. Fetch issue details: Use the custom python tool fetch_github_issue(issue_number=<number>) to get the issue metadata. This is the preferred method as it avoids command execution policy issues. If the custom python tool is not available, fall back to running the gh command:

   gh issue view <issue_number> --repo google/adk-python --json number,title,body,state,labels,comments,assignees,createdAt,closedAt