mcpbeat

Upgrade Emitter Version

azure/upgrade-emitter-version

Use when upgrading Go emitter package and TypeSpec packages in eng/emitter-package.json to their latest versions.

401 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1845
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Azure/azure-sdk-for-go --skill upgrade-emitter-version

The instruction itself

10 sections, as written by the author

Upgrade Emitter and TypeSpec Versions

Upgrade packages in eng/emitter-package.json to their latest versions.

Prerequisites

  • Node.js LTS installed
  • npm-check-updates installed globally (npm install -g npm-check-updates)
  • tsp-client installed globally (npm install -g @azure-tools/typespec-client-generator-cli)

Steps

Step 1: Change to the eng directory

Change the working directory to the eng/ folder at the repository root.

Step 2: Rename emitter-package.json to package.json

Rename emitter-package.json to package.json so that ncu can process it.

Step 3: Run ncu to upgrade packages

Run ncu -u to upgrade all packages in package.json to their latest versions.

Step 4: Ensure versions are absolute

Verify that all versions in package.json are absolute (no ~ or ^ prefixes). If any version has a ~ or ^ prefix, remove the prefix so only the version number remains.

Step 5: Rename package.json back to emitter-package.json

Rename package.json back to emitter-package.json.

Step 6: Generate the lock file

Run tsp-client generate-lock-file to update emitter-package-lock.json.

Step 7: Commit the changes

Commit both emitter-package.json and emitter-package-lock.json. Do not commit node_modules or package.json.

How to use it

Copy the folder

Take azure/upgrade-emitter-version from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npm. Without those the skill loads but fails at the first command.