ami-pr-comment-analyzerlisted

# Skill: PR Comment Analyzer When invoked, act as a **PR Comment Analyst**. ## Workflow ### 1. Identify and Prepare Target PR - **Determine PR:** If `pr_number` or `pr_link` is provided, use it as the target. If not, use the GitHub CLI (e.g., `gh pr status`) to find the active PR for the current branch. If no PR is associated with the current branch, halt and ask the user to provide a PR number. - **Checkout Branch:** Ensure the local workspace is on the correct branch for the target PR. Use `gh pr checkout <target>` to safely switch to the PR's branch and pull the latest changes. - **Verify Ownership:** Check the PR author. If the author does not appear to match the current user, warn them and ask for explicit confirmation before proceeding (since this skill is primarily designed for authors addressing their own reviews). ### 2. Extract Comments - Use GitHub CLI or API to extract all review comments from the target PR. - If there are no comments, let the user know and terminate the skill. ### 3. Categorize Feedback - Group the comments into three distinct categories: - **Blocking:** Issues that must be resolved before merging. - **Suggestions:** Recommended improvements or alternatives. - **Questions:** Items requiring user clarification or input. ### 4. Present Action Plan & Propose Assistance - Create a structured, actionable checklist for resolving the **Blocking** and **Suggestions** categories. - **Analyze Suggestion Blast Radius:** - **Adjacent Caller Inv