management-autopr-review

Reviews generated Azure Java management-library AutoPR changes for high-value generation risks.

2.6k|2.2k|Updated Dec 6, 2011
One-click install
npx skills add https://github.com/Azure/azure-sdk-for-java --skill management-autopr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: management-autopr-review
Source: https://github.com/Azure/azure-sdk-for-java/tree/main/.github/skills/management-autopr-review
Command: npx skills add https://github.com/Azure/azure-sdk-for-java --skill management-autopr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about management-autopr-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an Azure management AutoPR with this skill?

Invoke the management-autopr-review skill against an eligible PR: non-draft, targeting main, titled with [AutoPR azure-resourcemanager-, and authored by azure-sdk automation accounts. The skill inspects changed non-generated Java files and emits a structured markdown review comment.

What defects does the management AutoPR review detect?

It detects service-folder mismatches, stable packages built on preview API versions, overlapping API-version generations, suspicious LRO response/header shapes, non-pageable list operations, suspicious Manager class names, GA breaking changes, and missing release-plan links.

Which pull requests are eligible for the AutoPR review?

Only Azure/azure-sdk-for-java PRs that are non-draft, target main, originate in the same repository, have a title containing [AutoPR azure-resourcemanager-, and are authored by azure-sdk, azure-sdk-automation[bot], or app/azure-sdk-automation.

Does the review approve, merge, or modify pull requests?

No. The review is strictly advisory: it does not approve, merge, modify code, or access the spec repository. Blocking and Warning items request one concrete human action or verification, while Informational items only provide context.

Why are generated Java files excluded from the review?

Files whose repository-relative path contains a generated segment are never reviewed, because generated churn is expected and would create false positives. POM-only, CHANGELOG-only, metadata-only, and generated-only pushes produce no comment at all.

How are repeated findings handled across new commits?

Findings reuse stable IDs across commits. When a new head SHA passes the Java gate, still-applicable prior items are marked Carried forward in the replacement comment rather than restated as New; only a changed API-version set re-emits MGMT-API-VERSION as New.