What problem does it solve?
Generated Azure management-library AutoPRs can ship subtle defects—stable packages built on preview APIs, modules placed in the wrong service folder, overlapping API-version generations, or suspicious LRO and list-operation shapes—that manual reviewers often miss in large generated diffs.
Core Features & Use Cases
- Rule-based advisory review: Applies ten stable rules (MGMT-FOLDER, MGMT-VERSION, MGMT-BREAKING, MGMT-LRO, MGMT-LIST-RETURN, and more) with Blocking, Warning, and Informational severities, each citing a repository-relative file and affected symbol.
- Java-change gating and deduplication: Skips generated-path files and POM/CHANGELOG-only pushes, and carries still-applicable findings forward across commits using stable concern IDs instead of re-raising them.
- Use Case: When the azure-sdk-automation bot opens an AutoPR titled
[AutoPR azure-resourcemanager-compute], the skill inspects the non-generated Java changes and emits a structured markdown review comment flagging, for example, a stable 2.1.0 package generated from a preview API version.
Quick Start
Use the management-autopr-review skill to review the synthetic PR whose GitHub responses and per-file patches are materialized under github-responses and pr-diff.