azsdk-common-apiview-feedback-resolution

---
name: azsdk-common-apiview-feedback-resolution
license: MIT
metadata:
  version: "1.0.0"
  distribution: shared
description: "Analyze and resolve APIView review feedback on Azure SDK PRs. **UTILITY SKILL**. USE FOR: APIView comments, API review feedback, SDK API surface changes. DO NOT USE FOR: general code review, non-APIView feedback. INVOKES: azure-sdk-mcp:azsdk_apiview_get_comments, azure-sdk-mcp:azsdk_customized_code_update, azure-sdk-mcp:azsdk_typespec_delegate_apiview_feedback, azure-sdk-mcp:azsdk_run_typespec_validation, azure-sdk-mcp:azsdk_package_generate_code."
compatibility: "azure-sdk-mcp server, SDK pull request with APIView review link"
---

# APIView Feedback Resolution

This skill analyzes and resolves APIView review feedback on Azure SDK pull requests by retrieving reviewer comments, categorizing them, and applying TypeSpec or customization updates that bring the SDK API surface into compliance before re-review.

## Triggers

USE FOR: APIView comments, API review feedback, SDK API surface changes
WHEN: "resolve APIView comments", "address API review feedback", "update SDK API surface after APIView"
DO NOT USE FOR: general code review, non-APIView feedback

## Rules

- Requires the `azure-sdk-mcp` server; there is no CLI fallback for retrieving APIView comments or applying TypeSpec changes.
- Retrieve and categorize APIView comments before making changes so fixes map to reviewer intent.
- Validate, regenerate, build, and test after applying fixes before requesting re-review.

## MCP Tools

| Tool                                                     | Purpose                                             |
| -------------------------------------------------------- | --------------------------------------------------- |
| `azure-sdk-mcp:azsdk_apiview_get_comments`               | Get APIView comments                                |
| `azure-sdk-mcp:azsdk_customized_code_update`             | Apply TypeSpec & code customization changes locally |
| `azure-sdk-mcp:azsdk_typespec_delegate_apiview_feedback` | Delegate to CCA pipeline                            |
| `azure-sdk-mcp:azsdk_run_typespec_validation`            | Validate TypeSpec                                   |
| `azure-sdk-mcp:azsdk_package_generate_code`              | Regenerate SDK                                      |

## Steps

1. **Retrieve** — Get APIView URL from SDK PR, run `azsdk_apiview_get_comments`.
2. **Categorize** — Group as Critical/Suggestions/Informational per [feedback steps](references/feedback-resolution-steps.md).
3. **Resolve** — Use `azsdk_customized_code_update` for TypeSpec changes; delegate via `azsdk_typespec_delegate_apiview_feedback` for complex cases.
4. **Validate** — Run validation, regenerate SDK, build and test.
5. **Confirm** — Verify all items addressed. If delegated, follow [post-delegation follow-up](references/feedback-resolution-steps.md#post-delegation-follow-up). Request re-review.

## Examples

- "Resolve the APIView comments on my SDK pull request"
- "What feedback did the API reviewer leave?"

## Troubleshooting

- **No comments**: Verify PR has APIView link and MCP server is connected.
- **Validation fails**: Re-run after fixing TypeSpec errors.
- **MCP unavailable**: Requires `azure-sdk-mcp` server; no CLI fallback. Connect the server and retry.

More agent context in Azure/azure-sdk-for-python

19 other files this repository gives its agents.

Also found in 5 other repositories

The same file, byte for byte, in the weekly crawl of public GitHub.

• Azure/azure-sdk-for-net6.1k
• Azure/azure-sdk-for-java2.6k
• Azure/azure-sdk-for-js2.3k
• Azure/azure-sdk598
• Azure/azure-sdk-tools134