agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/azure-sdk-for-rust/.github/skills/update-emitter/SKILL.md

update-emitter

Skill887 starsChanged 29 days agoMITView on GitHub

Update the TypeSpec emitter for Rust and optionally regenerate all clients

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run eng/scripts/Update-Emitter.ps1 to update eng/emitter-package.json to the latest @azure-tools/typespec-rust version and regenerate the …

    line 8
  2. Distinctive:

    After updating the emitter, service crates should be regenerated to pick up the new version.

    line 12
  3. Very specific:

    Use the repository-pinned tsp-client.

    line 14
  4. Very specific:

    Run tsp-client with npm exec --prefix "$_TspClientDir" --no -- while the current directory is the client library root.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Update the TypeSpec emitter

Run eng/scripts/Update-Emitter.ps1 to update eng/emitter-package.json to the latest @azure-tools/typespec-rust version and regenerate the lock file.

Regenerating clients

After updating the emitter, service crates should be regenerated to pick up the new version.

Use the repository-pinned tsp-client; do not invoke a globally installed binary. From the repository root, install its locked dependencies:

_TspClientDir="$(pwd)/eng/common/tsp-client"
npm ci --prefix "$_TspClientDir"

Run tsp-client with npm exec --prefix "$_TspClientDir" --no -- while the current directory is the client library root. Service owners should regenerate only their own service crates.

To regenerate a single crate:

cd sdk/{service-directory}/{crate-directory}
npm exec --prefix "$_TspClientDir" --no -- tsp-client update

To regenerate all crates under a service directory from the repository root:

find sdk/{service-directory} -name tsp-location.yaml -execdir \
  npm exec --prefix "$_TspClientDir" --no -- tsp-client update \;

See eng/common/tsp-client/README.md for prerequisites, additional commands, and package management details.

After regenerating

  • Build and test each affected crate to verify correctness.
  • Review any changes to public APIs and update each crate's CHANGELOG.md accordingly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free