skills.rest
NVIDIA
NVIDIAOFFICIAL
Explore all skills by this author →
WebsiteGitHub

nemoclaw-contributor-update-dependencies

Audit and implement dependency upgrades as semantic migrations across upstream release ranges.

22.3k|3.1k|Updated Mar 15, 2026
Search Tags:#supply chain#version bump#dependency upgrade#Hermes#release audit#semantic migration#contract tracing
One-click install
npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-contributor-update-dependencies
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nemoclaw-contributor-update-dependencies
Source: https://github.com/NVIDIA/NemoClaw/tree/main/.agents/skills/nemoclaw-contributor-update-dependencies
Command: npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-contributor-update-dependencies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Upgrading a dependency is rarely a one-line version bump: upstream releases change contracts, defaults, and artifacts that silently break downstream consumers. This Skill turns a dependency upgrade into a structured migration by auditing every adjacent release range, mapping changed upstream contracts to current NemoClaw consumers, and verifying the exact artifacts and selectors the change ships.

Core Features & Use Cases

  • Release-range auditing: Builds a release ledger of adjacent upstream ranges using the checked-in collector scripts, resolving immutable source, tag, package, and image identities instead of trusting version strings.
  • Contract-to-consumer tracing: Maps each changed upstream contract (commands, APIs, configuration, credentials, lifecycle, packaging) to its downstream consumer and records one reviewable concern per failure mode.
  • Hermes upgrade variant: Handles Hermes CalVer releases with a dedicated supplement script and a base-image publication procedure that pins immutable image digests.
  • Use Case: When bumping the pinned Hermes release in NemoClaw, the Skill reconciles published releases with the upstream clone, audits each adjacent range, migrates affected consumers in release order, and verifies the final image and selectors before handoff.

Quick Start

Ask the agent to upgrade a specific NemoClaw dependency to a target version and audit what the change breaks downstream.

Frequently Asked Questions about nemoclaw-contributor-update-dependencies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely upgrade a dependency in NemoClaw?▼

Treat the upgrade as a migration: audit every adjacent upstream release range, map changed contracts to current NemoClaw consumers, implement migrations in release order, and verify the artifacts and selectors the PR head uses. The Skill's collector scripts produce deterministic release-ledger evidence for this audit.

How do I audit upstream release changes before bumping a version?▼

Use the release-ledger workflow: resolve immutable source identities for each adjacent range, inspect every commit and changed path, and treat release notes as leads rather than behavior authority. The collect-release-ledger.py script gathers bounded, hermetic Git and GitHub evidence for each range.

Does this Skill handle Hermes release upgrades?▼

Yes. A conditional Hermes variant covers multi-component CalVer tags using the collect-hermes-release-supplement.py script, which reconciles published stable releases with a complete local clone. It also defines the base-image publication procedure that pins immutable image digests.

Can the dependency upgrade workflow modify the upstream repository?▼

No. The mutation boundary restricts changes to the NemoClaw checkout; upstream repositories, registries, workflows, and PRs are read-only. Upstream defects are reported with their downstream effect, and any upstream change requires a separate explicit user request.

What evidence is required before a dependency upgrade is considered done?▼

Every recorded concern needs a disposition backed by revision-bound evidence such as source and tests, resolved dependency graphs, immutable artifacts, or runtime behavior. Aggregate CI passes, version output, or release-note silence alone cannot close a material concern.

Related Skills

Explore More Software Engineering Skills→
receptronreceptron
41

release-notes

Generate release notes from merged pull requests since the previous tag.

Official
Advanced
steilerDevsteilerDev
4

fix-e2e

Categorize failing E2E CI failures by root cause and plan fixes.

Community
Advanced
alivecontextalivecontext
124

alive:system-upgrade

Migrate ALIVE Context Systems from legacy formats to v3 structure.

Official
Advanced
sdcorejssdcorejs
2

sdcorejs-dep-update

Run safe npm/yarn/pnpm dependency upgrades with lockfile diff checks.

Community
Advanced