codegen

# TypeSpec Code Generation (tsp-client) Use this skill to run `tsp-client` workflows for projects that include a `tsp-location.yaml` file. ## Preconditions - You must be in the directory that contains `tsp-location.yaml`. - If the file is missing, warn the user and ask for the correct directory (do not run commands). ## Commit hash update If the user provides a commit hash, update the `commit:` field in `tsp-location.yaml` **before** running tsp-client. - Read the file and locate the `commit:` line. - Replace the value with the provided hash (keep the same key name and formatting). - Example: - Before: `commit: 6267b6...` - After: `commit: <new_hash>` ## Commands ### `tsp-client update` Pull the latest codegen tooling or definitions (default action when the user is vague). ```bash tsp-client update ``` ### `tsp-client sync` Fetch/sync TypeSpec inputs for the project. ```bash tsp-client sync ``` ### `tsp-client generate` Generate code from TypeSpec inputs. ```bash tsp-client generate ``` Keep the synced TypeSpec inputs: ```bash tsp-client generate --save-inputs ``` ## Steps 1. Verify `tsp-location.yaml` exists in the current directory. If not, stop and ask for the correct location. 2. If the user provided a commit hash, update the `commit:` value in `tsp-location.yaml`. 3. Determine the user intent: - **Refresh/update/ingest changes from a commit**: run `tsp-client update`. - **Fetch/sync spec from the current commit**: run `tsp-client sync`. - **Generate from fetched spec**: run `tsp-client generate` (use `--save-inputs` only if the user asks to keep inputs). - **Generate (no fetch requested)**: run `tsp-client generate`. 4. If the user doesn’t specify, default to `tsp-client update`. 5. If the project defines or creates a `TempTypeSpecFiles` folder and the user wants code generation, run `tsp-client generate` (with `--save-inputs` if requested). 6. If a tsp-client command fails, report the error output and suggest checking the TypeSpec repo/commit referenced in `tsp-location.yaml`. Build a GitHub URL from `repo:` and `directory:` (and include the `commit:` as the ref), e.g.: - Repo: `Azure/azure-rest-api-specs` - Commit: `6267b6...` - Directory: `specification/cognitiveservices/OpenAI.Inference` - URL: `https://github.com/Azure/azure-rest-api-specs/tree/6267b6.../specification/cognitiveservices/OpenAI.Inference`