agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/NeMo-Relay/.agents/skills/rename-surfaces/SKILL.md

rename-surfaces

Skill238 starsChanged 2 months agoApache-2.0View on GitHub

Rename a NeMo Relay repository, package, crate, module, public symbol, import path, or brand surface across multiple consumers. Do not use for a file-local private rename.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for coordinated naming changes such as repository renames, crate prefix changes, package/module renames, import-path …

    line 10
  2. Very specific:

    Update generated or generated-from-build surfaces such as crates/ffi/nemo_relay.h through the proper build step.

    line 28
  3. Distinctive:

    Search for old names after the rename and validate every public language surface.

    line 30

≈ “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

Perform A Repo Rename Or Surface Rename

Use this skill for coordinated naming changes such as repository renames, crate prefix changes, package/module renames, import-path changes, FFI symbol renames, or branding text updates that must preserve functional identifiers.

Rename Buckets To Audit

  • Repository references
  • Rust crate names and module prefixes
  • Python package name and top-level module
  • Go module path and package paths
  • Node package names
  • C header names and symbol prefixes
  • Docs, examples, CI, and integration packages

Rules

  • Separate branding text from functional identifiers.
  • Preserve repository and import paths exactly where code depends on them.
  • Update generated or generated-from-build surfaces such as crates/ffi/nemo_relay.h through the proper build step.
  • Search for old names after the rename and validate every public language surface.

Checklist

  • Manifests updated
  • Source imports and symbol names updated
  • Docs and examples updated
  • Integration packages and scripts updated
  • No stale old names remain in tracked files where they would break behavior
  • Every surface changed by the rename has focused validation

References

  • README.md
  • docs/getting-started/quick-start/index.mdx
  • docs/reference/api/index.mdx

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