How do I install the Codegen skill?

Run npx skillmds@latest add azure-azure-sdk-for-java/codegen in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Codegen safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Codegen?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Codegen free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Codegen?

Azure (@azure-azure-sdk-for-java) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Codegen by azure-azure-sdk-for-java

Name: Codegen
Rating: 4.666666666666667 (3 reviews)
Author: Azure

File contents

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).

tsp-client update

`tsp-client sync`

Fetch/sync TypeSpec inputs for the project.

tsp-client sync

`tsp-client generate`

Generate code from TypeSpec inputs.

tsp-client generate

Keep the synced TypeSpec inputs:

tsp-client generate --save-inputs

Steps

Verify tsp-location.yaml exists in the current directory. If not, stop and ask for the correct location.
If the user provided a commit hash, update the commit: value in tsp-location.yaml.
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.
If the user doesn’t specify, default to tsp-client update.
If the project defines or creates a TempTypeSpecFiles folder and the user wants code generation, run tsp-client generate (with --save-inputs if requested).
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

---name: codegendescription: Generate code from TypeSpec via tsp-client (update, sync, generate). Requires a tsp-location.yaml in the current working directory. Supports updating the commit hash before running.---# 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 updateIf 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).```bashtsp-client update```### `tsp-client sync`Fetch/sync TypeSpec inputs for the project.```bashtsp-client sync```### `tsp-client generate`Generate code from TypeSpec inputs.```bashtsp-client generate```Keep the synced TypeSpec inputs:```bashtsp-client generate --save-inputs```## Steps1. 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`

Frequently asked questions

Codegen