Azure SDK for .NET is a repository containing the actively developed C# libraries that applications use to work with Azure services. It is for .NET developers building software that connects to Azure storage, management, and other cloud services.
Borrowing it
Nothing to install: this file belongs to Azure/azure-sdk-for-net. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Azure/azure-sdk-for-net/main/.github/skills/mgmt-review-comment-resolution/SKILL.mdgit clone --depth 1 https://github.com/Azure/azure-sdk-for-netWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/azure/azure-sdk-for-net/mgmt-review-comment-resolution)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-net/mgmt-review-comment-resolution"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/mgmt-review-comment-resolution/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/azure/azure-sdk-for-net/mgmt-review-comment-resolution"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/mgmt-review-comment-resolution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00046 | $0.02543 |
| Opus 5 | $0.00023 | $0.01272 |
| Sonnet 5 | $0.00009 | $0.00509 |
| Haiku 4.5 | $0.00005 | $0.00254 |
Grade A, and why
mgmt-review-comment-resolution 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 11d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: mgmt-review-comment-resolution
Resolve review comments on Azure management-plane SDK PRs by making changes in the TypeSpec spec repo (client.tsp) and regenerating the SDK.
When Invoked
Trigger phrases: "resolve review comments", "fix review comments", "resolve PR comments", "rename types", "fix naming", "resolve naming comments", "fix API surface".
Overview
Management-plane SDK code is generated from TypeSpec definitions in azure-rest-api-specs. Review comments on SDK PRs often request changes to the generated API surface — renaming types, renaming properties, or changing property types to be more user-friendly. These changes are made in the spec repo's client.tsp using TypeSpec decorators (primarily @@clientName), then the SDK is regenerated.
Key Concepts
@@clientName(TypeSpecName, "CSharpName", "csharp")— renames a TypeSpec model/union/enum/property to a different name in the generated C# SDK. This is the primary tool for resolving naming comments.@@clientNameonly works on types defined in the service's TypeSpec — you can only target models, unions, enums, and interfaces that are explicitly declared in the service's.tspfiles. If a type is not defined there (e.g., it comes from ARM common types or TypeSpec templates),@@clientNamecannot target it. See "Renaming via SDK Custom Code" below.@@clientNamecannot target aliases — if a type is defined as analias,@@clientNamecannot target it. See "Handling Unsupported Cases" below.- Only
client.tspmay be changed in the spec repo — do not modify any other.tspfiles or config files. If resolving a comment would require changes to other files, skip that change and inform the user with the reason after processing all other comments. Since onlyclient.tspis modified, swagger regeneration is never needed.
Types of Review Comments
1. Type Names Too Generic
Review comments may flag type names that are too generic and could collide with types from other SDKs or lack sufficient context.
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.
- 11d ago First seen · 193 lines · 46 tokens per session scan A 1015b6aba730
mgmt-review-comment-resolution is a skill published in the GitHub repository Azure/azure-sdk-for-net (6,050 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 2,543 once invoked, about $0.0002 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.
Other skills, from other repositories
cosmos-pre-commit-validation
Run pre-commit checks for a specific set of crates. Use this when validating changes under sdk/cosmos before committing or during code review.
cosmos-design-struct
Enforce consistent struct design conventions across sdk/cosmos crates. Validates visibility modifiers, field privacy, #[nonexhaustive] usage, and construction API patterns (Default/new with with setters, or optional separate builders with builder()/build()), and construction correctness on public structs. Can auto-fix…
update-pr
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.
clean-abap
Clean ABAP coding standards and best practices. Use when writing ABAP code, reviewing ABAP code, or refactoring ABAP code to ensure it follows SAP's official Clean ABAP style guide. Covers naming conventions, modern language constructs, class/method design, error handling, formatting, comments, and unit testing…
code-analysis
Use the free built-in .NET SDK analyzers and analysis levels with gradual Roslyn warning promotion. USE FOR: the repo wants first-party .NET analyzers; CI should fail on analyzer warnings; the team needs AnalysisLevel or AnalysisMode guidance. DO NOT USE FOR: third-party analyzer selection by itself; formatting-only…
sonarjs
Use SonarJS-derived rules in .NET repositories that ship JavaScript or TypeScript frontends and need deeper bug-risk, code-smell, or cognitive-complexity checks than a minimal ESLint baseline. USE FOR: SonarQube, SonarCloud, or eslint-plugin-sonarjs setups; frontend code smells; cognitive complexity and deeper…