What is management-autopr-review?

A focused review tool for selected Azure Java management-library pull requests, which are proposed code changes shared for review, created automatically by Azure’s code-generation process.

It is for checking qualifying non-draft changes on the main branch, including release-plan links and other listed generation risks, without approving, merging, or editing code.

It catches specific high-risk problems in generated changes without treating every file or pull request as eligible for review.

management-autopr-review — Skill by Azure

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/azure/azure-sdk-for-java/management-autopr-review

Any agent

npx skills add Azure/azure-sdk-for-java --skill management-autopr-review

Clone the repo

git clone --depth 1 https://github.com/Azure/azure-sdk-for-java

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,421 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00025	$0.02421
Opus 5	$0.00013	$0.01210
Sonnet 5	$0.00005	$0.00484
Haiku 4.5	$0.00003	$0.00242

Measured yesterday against content hash fcb1498d5065, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

management-autopr-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/management-autopr-review/SKILL.md · 257 lines

How it starts

The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Management AutoPR Review Rules

Use only for 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.

The review is advisory. It does not approve, merge, modify code, access the spec repository, or replace other automated and human review.

Java-change gate

Never review a file whose normalized repository-relative path contains a generated segment ((^|/)generated(/|$)). This includes generated samples and tests.

Review opened, reopened, and ready_for_review only when the PR contains a changed .java file outside a generated path. On synchronize, review only when the pushed before..after range changes such a .java file. POM-only, CHANGELOG-only, metadata-only, generated-only, and refresh-only pushes produce no comment.

Once the Java gate passes, supporting POM, CHANGELOG, metadata, and CI files may be read as evidence, except files under a generated path.

Review rules

`MGMT-RELEASE-PLAN`: missing release-plan link

Severity: Warning

Normalize casing and Markdown emphasis. Accept both plain Release Plan link: https://example.com/release-plan and formatted **Release plan link:** [text](https://example.com/release-plan). Require an HTTP(S) URL.

Report when the PR description contains no accepted release-plan link. Cite the PR description and continue the remaining review passes so other high-value concerns are not hidden.

`MGMT-FOLDER`: service-folder mismatch

Severity: Blocking

For a newly added management module, split its directory name on -. The expected service identity is always the third segment:

azure-resourcemanager-<service-identity>[-<module-suffix>...]

Ignore the fourth and later segments when comparing the module with its sdk/<service>/ folder. For example, azure-resourcemanager-compute-bulkactions belongs in sdk/compute.

Read the full file on GitHub · 257 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 257 lines · 25 tokens per session scan A fcb1498d5065

Subscribe to this mod's changes

management-autopr-review is a skill published in the GitHub repository Azure/azure-sdk-for-java (2,566 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 2,421 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review DevOps and cloud Git and workflow azure azure-resources azure-sdk azure-services java media

dpg-migration

Migration logic for Azure SDK for .NET data-plane libraries migrating from AutoRest/Swagger to TypeSpec-based generation. Uses MCP tools from the generator-agent server for automated deterministic fixes.

Azure/azure-sdk-for-net · 41 tokens

csharp-azure-spector-coverage-gaps

Discovers and implements gaps in Spector test coverage for the Azure C# HTTP client emitter. Use when asked to find missing Spector scenarios, add Spector test coverage, or implement a specific Spector spec for the Azure C# emitter. Can also compare coverage between the Azure dashboard and the Standard (TypeSpec core)…

Azure/azure-sdk-for-net · 78 tokens

auto-build-repair

Headless, bounded repair of custom-code build failures in an already-generated Azure SDK PR. Thin wrapper over the shared azure-sdk-mcp:azsdkcustomizedcodeupdate engine in custom-code-only scope (editScope: CustomCode); the skill owns the iterate-until-green loop, capped by a per-language maxIterations read from…

Azure/azure-sdk-for-net · 149 tokens

azure-sdk-mgmt-pr-review

Review Azure SDK management-plane pull requests, check naming conventions, API compatibility, and code quality.

Azure/azure-sdk-for-net · 26 tokens

mgmt-review-comment-resolution

Resolve review comments on Azure management-plane .NET SDK PRs. Handles renaming types/properties, changing property types, and other API surface adjustments by updating TypeSpec client.tsp and regenerating.

Azure/azure-sdk-for-net · 46 tokens

mitigate-breaking-changes

Patterns and techniques for mitigating breaking changes during Azure management-plane SDK migration from Swagger/AutoRest to TypeSpec. Covers SDK-side customizations (partial classes, CodeGenType, CodeGenSuppress) and TypeSpec decorator customizations (clientName, access, markAsPageable, alternateType…

Azure/azure-sdk-for-net · 68 tokens