You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/skills/azsdk-common-generate-sdk-locally/references/customization-workflow.md
+21-20Lines changed: 21 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,15 +6,15 @@ The customization workflow is an AI-assisted process that applies TypeSpec decor
6
6
7
7
The customization tool (`azure-sdk-mcp:azsdk_customized_code_update`) can be triggered from multiple sources:
8
8
9
-
| Entry Point | Description | Example |
10
-
|-------------|-------------|---------|
11
-
|**Build failures**| Compilation errors, analyzer violations, linting failures after SDK generation |`error CS0246: The type or namespace name 'FooModel' could not be found`|
12
-
|**Breaking changes**| Output from breaking changes analysis tools detecting renamed/removed properties, changed types |`Breaking changes detected: FooOptions.timeout property type changed from int to Duration`|
13
-
|**User prompts**| Natural language requests to modify SDK behavior | "Rename FooClient to BarClient for .NET" |
14
-
|**API review feedback**| Feedback from APIView or PR comments on SDK naming/structure | "Model name doesn't follow .NET casing conventions" |
15
-
|**.NET analyzer errors**| AZC0030 (naming violations), AZC0012 (generic type names), etc. |`AZC0030: Model name ends with 'Parameters'`|
|**Duplicate field conflicts**| TypeSpec adds a property that already exists in manual customization code |`variable operationId is already defined in class AnalyzeOperationDetails`|
|**Build failures**| Compilation errors, analyzer violations, linting failures after SDK generation |`error CS0246: The type or namespace name 'FooModel' could not be found`|
12
+
|**Breaking changes**| Output from breaking changes analysis tools detecting renamed/removed properties, changed types |`Breaking changes detected: FooOptions.timeout property type changed from int to Duration`|
13
+
|**User prompts**| Natural language requests to modify SDK behavior | "Rename FooClient to BarClient for .NET"|
14
+
|**API review feedback**| Feedback from APIView or PR comments on SDK naming/structure | "Model name doesn't follow .NET casing conventions"|
15
+
|**.NET analyzer errors**| AZC0030 (naming violations), AZC0012 (generic type names), etc. |`AZC0030: Model name ends with 'Parameters'`|
|**Duplicate field conflicts**| TypeSpec adds a property that already exists in manual customization code |`variable operationId is already defined in class AnalyzeOperationDetails`|
18
18
19
19
## When to Use
20
20
@@ -44,17 +44,17 @@ The customization tool (`azure-sdk-mcp:azsdk_customized_code_update`) can be tri
44
44
45
45
## Common Scenarios
46
46
47
-
| Scenario | Phase | Customization |
48
-
|----------|-------|--------------|
49
-
| Type name conflict with reserved keyword | A | Rename via `@@clientName` in `client.tsp`|
50
-
| Property renamed in new API version | A | Add `@@clientName` to preserve backward compatibility |
51
-
| .NET analyzer error (AZC0030, AZC0012) | A | Apply scoped `@@clientName` decorators to fix naming violations |
52
-
| Hide internal operation from SDK | A | Apply `@@access` decorator with language scope |
53
-
| Create subclient architecture | A | Use `@client` and `@clientInitialization` decorators |
54
-
| API review naming feedback | A | Apply scoped `@@clientName` for specific language |
55
-
| Duplicate field from customization conflict | B | Remove duplicate `addField()` from customization class |
56
-
| Customization references renamed property | B | Update references in `_patch.py`, `*Customization.java`, or partial classes |
57
-
| Feature request with no TypeSpec solution | Manual | Tool provides guidance to create customization infrastructure |
@@ -22,7 +24,7 @@ There are two commit checkpoints in the workflow. At each one:
22
24
1. Inform the user that the preceding steps completed successfully.
23
25
2.**Prompt the user** to decide whether to commit now. Do NOT skip this prompt.
24
26
3. If user chooses to commit:
25
-
- Check if on the `main` branch. If so, prompt: *"You are currently on the main branch. Please create a new branch using `git checkout -b <branch-name>` before proceeding."* Suggest a default branch name (e.g., `sdk/<service-name>/<package-name>`).
27
+
- Check if on the `main` branch. If so, prompt: _"You are currently on the main branch. Please create a new branch using `git checkout -b <branch-name>` before proceeding."_ Suggest a default branch name (e.g., `sdk/<service-name>/<package-name>`).
26
28
- Stage changed files with `git add`.
27
29
- Prompt for a commit message, then run `git commit -m "<message>"`.
Copy file name to clipboardExpand all lines: .github/skills/azsdk-common-pipeline-troubleshooting/SKILL.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ license: MIT
4
4
metadata:
5
5
version: "1.0.0"
6
6
distribution: shared
7
-
description: "Diagnose and resolve failures in Azure SDK CI and generation pipelines. **UTILITY SKILL**. USE FOR: \"pipeline failed\", \"build failure\", \"CI check failing\", \"SDK generation error\", \"reproduce pipeline locally\", \"debug SDK pipeline\". DO NOT USE FOR: local build issues without pipeline context, API design review, SDK publishing. INVOKES: azure-sdk-mcp:azsdk_analyze_pipeline, azure-sdk-mcp:azsdk_verify_setup, azure-sdk-mcp:azsdk_package_build_code, azure-sdk-mcp:azsdk_package_run_check, azure-sdk-mcp:azsdk_package_pack."
7
+
description: 'Diagnose and resolve failures in Azure SDK CI and generation pipelines. **UTILITY SKILL**. USE FOR: "pipeline failed", "build failure", "CI check failing", "SDK generation error", "reproduce pipeline locally", "debug SDK pipeline". DO NOT USE FOR: local build issues without pipeline context, API design review, SDK publishing. INVOKES: azure-sdk-mcp:azsdk_analyze_pipeline, azure-sdk-mcp:azsdk_verify_setup, azure-sdk-mcp:azsdk_package_build_code, azure-sdk-mcp:azsdk_package_run_check, azure-sdk-mcp:azsdk_package_pack.'
2. Run `azsdk_link_sdk_pull_request_to_release_plan` for each PR, passing the Release Plan ID or work item ID as `workItemId` (or as `releasePlanId`) — either value is accepted.
56
+
2. Run `azsdk_link_sdk_pull_request_to_release_plan` for each PR, passing the Release Plan ID or work item ID as `workItemId` (or as `releasePlanId`) — either value is accepted.
![azure-sdk-automation[bot]](https://avatars.githubusercontent.com/in/1086291?v=4&size=40){kind=avatar}
0 commit comments