Sync eng/common directory with azure-sdk-tools for PR 11868 (#52707)

* added instructions for sdk local workflow

* fix case

* Added missing comma

* Update eng/common/instructions/azsdk-tools/local-sdk-workflow.instructions.md

Co-authored-by: Mariana Rios Flores <[email protected]>

* Update eng/common/instructions/azsdk-tools/local-sdk-workflow.instructions.md

Co-authored-by: Mariana Rios Flores <[email protected]>

* Update eng/common/instructions/azsdk-tools/local-sdk-workflow.instructions.md

Co-authored-by: Mariana Rios Flores <[email protected]>

* Update eng/common/instructions/azsdk-tools/local-sdk-workflow.instructions.md

Co-authored-by: Mariana Rios Flores <[email protected]>

* Replace 'tspconfigPath' by the literal file name

* Added routing step to choose workflow

* Added goal and action to some steps properly

* Specified mcp tool name explicitly

* Added back step to choose sdk generation approach

* Specified the mcp tool names explicitly

* Update eng/common/instructions/azsdk-tools/local-sdk-workflow.instructions.md

Co-authored-by: Mariana Rios Flores <[email protected]>

---------

Co-authored-by: ray chen <[email protected]>
Co-authored-by: Mariana Rios Flores <[email protected]>

eng/common/instructions/azsdk-tools/local-sdk-workflow.instructions.md

@@ -0,0 +1,119 @@
+---
+description: "Guide the user to generate and build SDKs locally for a TypeSpec based API spec"
+---
+
+# Goal
+
+Help the user generate and build SDKs locally from TypeSpec API specifications using the `azure-sdk-mcp` tools.
+
+---
+
+## Part A: Generate SDK Locally
+
+### Step 1: Outline workflow
+
+**Goal**: Ensure the user understands the overall SDK generation and build process before starting.  
+**Actions**:
+
+- Present the high-level steps involved in generating and building SDK locally:
+  1. Select target language
+  2. Verify SDK repository
+  3. Validate repository path
+  4. Identify path to configuration file
+  5. Generate SDK using `azsdk_package_generate_code` MCP tool
+  6. Identify SDK project path
+  7. Build/Compile SDK using `azsdk_package_build_code` MCP tool
+- Ask the user to confirm readiness to proceed.
+
+---
+
+### Step 2: Select language
+
+**Goal**: Confirm the target language for SDK generation.  
+**Actions**:
+
+- Prompt user to choose one of the supported languages:
+  - .NET
+  - Java
+  - JavaScript
+  - Python
+  - Go
+- Validate input against the allowed list.
+
+---
+
+### Step 3: Verify SDK repository
+
+**Goal**: Ensure the correct Azure SDK language repository is available locally.
+**Actions**:
+
+- Prompt user to provide the path to their **locally cloned repository** for the selected language.
+- Note: The **local folder name can be arbitrary**, but the repository must have originated from one of the official Azure SDK repositories:
+  - `azure-sdk-for-net` (.NET)
+  - `azure-sdk-for-java` (Java)
+  - `azure-sdk-for-js` (JavaScript)
+  - `azure-sdk-for-python` (Python)
+  - `azure-sdk-for-go` (Go)
+- If the repository is not cloned → instruct user to clone the appropriate remote repository from GitHub.
+- MCP tool will automatically validate the remote origin and repository structure.
+
+---
+
+### Step 4: Validate repository path
+
+**Actions**:
+
+- Check if the provided repository path exists and matches the selected SDK language repository.
+- If invalid → prompt user to re-enter a valid path.
+
+---
+
+### Step 5: Identify path to configuration file
+
+**Goal**: Determine the correct path to the TypeSpec configuration file based on the working context.  
+**Actions**:
+
+- **Scenario A: Working in a repository cloned from `azure-rest-api-specs`**
+  - Identify the path to `tspconfig.yaml` (local path or HTTPS URL).
+  - The local folder name can be arbitrary; the MCP tool will validate that the remote origin URL points to the official `azure-rest-api-specs` repository.
+  - Example paths (pointing directly to tspconfig.yaml):
+    - `/home/usr/azure-rest-api-specs/specification/contosowidgetmanager/Contoso.Management/tspconfig.yaml`
+    - `https://github.com/Azure/azure-rest-api-specs/blob/4af373fc5826cf5a2365a20dde01c4b2efde48f0/specification/contosowidgetmanager/Contoso.Management/tspconfig.yaml`
+
+- **Scenario B: Working in one of the official Azure SDK language repositories**  
+  (i.e., originally cloned from `azure-sdk-for-net`, `azure-sdk-for-java`, `azure-sdk-for-js`, `azure-sdk-for-python`, `azure-sdk-for-go`)
+  - Identify the path to `tsp-location.yaml`.
+  - The local folder name can be arbitrary; MCP tool will validate the remote origin URL.
+  - Example path:
+    `/home/usr/azure-sdk-for-net/sdk/contoso/Azure.ResourceManager.Contoso/tsp-location.yaml`
+
+---
+
+### Step 6: Generate SDK
+
+**Actions**:
+
+- Run `azsdk_package_generate_code` MCP tool to generate the SDK locally.
+
+---
+
+## Part B: Build / Compile SDK Locally
+
+### Step 1: Identify SDK project path
+
+**Goal**: Locate the generated SDK project directory for building/compiling.
+**Actions**:
+
+- Find the project directory inside the selected Azure SDK language repository.
+- Typical structure:  
+  `sdk/{service-name}/{package-name}/`
+- Example:  
+  `/path/to/azure-sdk-for-net/contoso/Azure.ResourceManager.Contoso/`
+
+---
+
+### Step 2: Build/Compile the SDK
+
+**Actions**:
+
+- Run `azsdk_package_build_code` MCP tool to compile the SDK in the identified project directory.

eng/common/instructions/azsdk-tools/typespec-to-sdk.instructions.md

@@ -57,10 +57,12 @@ Wait for the user to respond with a confirmation before proceeding to Step 1. Us
 **Goal**: Determine how to generate SDKs
 **Actions**:
 1. Present options: "How would you like to generate SDKs?"
-    - Option A: "Generate SDK locally". This is currently supported only for Python. Do not recommend this for other languages.
+    - Option A: "Generate SDK locally".
     - Option B: "Use SDK generation pipeline"
 2. Based on selection:
-    - If Option A: Refer to #file:create-sdk-locally.instructions.md and then proceed to Step 6
+    - If Option A: 
+        - Follow #file:./local-sdk-workflow.instructions.md to generate and compile the SDK.
+        - After SDK has been generated, to continue the SDK release, users can create the SDK pull request manually then proceed to Step 9.
     - If Option B: Continue to Step 6
 **Success Criteria**: SDK generation method selected