chatandbuild/Azure Sdk Mgmt Pr Review
skills/azure-sdk-mgmt-pr-review/SKILL.md
Use this skill when reviewing Azure SDK management-plane pull requests for API compatibility, naming conventions, generated-code expectations, breaking changes, and SDK quality standards.
$ install --global
skillsauthnpx skillsauth add chatandbuild/chatchat-skills Azure Sdk Mgmt Pr ReviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 14, 2026, 3:20 AM185.0s2 files scanned
SKILL.md
- id:
- azure-sdk-mgmt-pr-review
- name:
- Azure Sdk Mgmt Pr Review
- description:
- Use this skill when reviewing Azure SDK management-plane pull requests for API compatibility, naming conventions, generated-code expectations, breaking changes, and SDK quality standards.
- category:
- Development
Azure .NET Mgmt SDK PR Review
Review Azure SDK for .NET management library pull requests against the official API review guidelines.
Instructions
When asked to review an Azure SDK .NET management-plane library PR (packages Azure.ResourceManager and Azure.ResourceManager.*):
- Fetch PR details and diff using GitHub MCP tools
- Examine API surface files (api/*.cs) for public API
- Check Generated models and resources in src/Generated/
- Review TypeSpec customizations (e.g.,
client.tsp,tspconfig.yaml) - Add review comments directly to the PR using GitHub MCP tools
Review Checklist
Naming - Avoid These Suffixes
| Suffix | Replace With | Exception | |--------|--------------|-----------| | Parameter(s) | Content/Patch | - | | Request | Content | - | | Options | Config | Unless ClientOptions | | Response | Result | - | | Data | - | Unless derives from ResourceData/TrackedResourceData | | Definition | - | Unless removing it creates conflict with another resource | | Operation | Data or Info | Unless derives from Operation<T> | | Collection | Group/List | Unless domain-specific (e.g., MongoDBCollection) |
Resource Naming
- Remove "Resource" suffix if remaining noun is still descriptive (e.g., VirtualMachine not VirtualMachineResource)
- Keep "Resource" if removing makes it non-descriptive (e.g., GenericResource stays)
- For models: append "Data" suffix if inherits ResourceData/TrackedResourceData, otherwise "Info"
Operation Body Parameters
- PATCH operation body: Must be named
[Model]Patch - PUT/POST operation body: Must be named
[Model]Contentor[Model]Data
Property Naming
- Boolean properties: Must start with verb prefix:
Is,Can,Has - DateTimeOffset properties: Should end with
On(e.g.,CreatedOn,StartOn,EndOn) - Interval/Duration (integer): Include units in name (e.g.,
MonitoringIntervalInSeconds) - TTL properties: Rename to
TimeToLiveIn<Unit>
Acronyms
- Use PascalCase (capitalize first letter only):
Aes,Tcp,Http - 2-letter acronyms: uppercase if standalone (
IO), exceptId,Vm - Expand acronyms if not clearly explained in first page of search results with context
Enums
- Use singular type name (not plural) unless bit flags
- Numeric version enums should use underscore:
Tls1_0,Ver5_6
Type Formatting
The following table applies to the generated C# API surface (public types/properties in api/*.cs).
| Property Pattern | Expected Type |
|------------------|---------------|
| Ends with Id/Guid with UUID value | Guid |
| Ends with Id with ARM resource ID | ResourceIdentifier |
| Named ResourceType or ends with Type for resource types | ResourceType |
| Named etag | ETag |
| Contains location/locations | Consider AzureLocation |
| Contains size | Consider int/long instead of string |
For TypeSpec, UUID-valued properties should use the uuid scalar and map to Guid in the generated .NET SDK.
Duration/Interval Format
- ISO 8601 duration (P1DT2H59M59S): use
durationscalar in TypeSpec - ISO 8601 constant (2.2:59:59.5000000): use
@encode(DurationConstant)in TypeSpec
CheckNameAvailability Operation
- Method:
Check[Resource/RP name]NameAvailability - Parameter/Response model:
[Resource/RP name]NameAvailabilityXXX - Unavailable reason enum:
[Resource/RP name]NameUnavailableReason
Other API Rules
- PUT/PATCH optional body parameters should be changed to required
- Discriminator models should make base model
abstract - Remove all
ListOperationsmethods (SDK exposes operations via public APIs)
Output Format
- Summarize what passes review
- For each issue found, add a review comment directly to the PR on the relevant file and line using GitHub MCP tools
- Provide a final summary of all comments added
Related Skills
chatandbuild/yeet
tools
VerifiedTrustedCommunity
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
1SKILL.mdUpdated Jul 22, 2026
chatandbuild/xlsx
development
VerifiedTrustedCommunity
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
1SKILL.mdUpdated Jul 22, 2026
chatandbuild/Workout Logger
development
VerifiedTrustedCommunity
Use this skill when turning messy workout information into clear logs, comparing user-provided sessions, surfacing trends or likely PRs, and suggesting realistic next-session steps.
1SKILL.mdUpdated Jul 22, 2026
chatandbuild/webapp-testing
tools
VerifiedTrustedCommunity
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
1SKILL.mdUpdated Jul 22, 2026