jetson-promote-image
Use to promote overlay files and built artifacts into the staged BSP image. Do NOT use to flash or build. Triggers: promote bsp image.
npx skills add NVIDIA/skills --skill jetson-promote-image --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Promote BSP Image stages every Customize-* and Build output into bsp_image/Linux_for_Tegra, preparing it for /jetson-flash-image. It copies files from an overlay tracker and a build manifest into the BSP image, using diff-aware logic, and may rebuild initramfs when kernel or modules change. It does not flash or build, and the two channels are overlay (Customize-*) and manifest (build outputs).
How it works
- Resolve active target and paths, defining LFT_SRC, LFT_DST, and MANIFEST from the workspace and profile.
- Validate channels: require at least one channel populated; check for uncommitted overlay changes and valid YAML manifest when present.
- Verify build-source freshness: ensure kernel-side repos are not dirty since last jetson-build-source.
- Pre-promote collision check (overlay only): ensure upstream remote commits are pulled if configured.
- Enumerate sources:
- Channel A (overlay): map src = LFT_SRC/<rel> to dst = LFT_DST/<rel> via git ls-files.
- Channel B (manifest): parse artifacts[].src/dst from MANIFEST and ensure src exists on disk.
- Diff-aware copy into bsp_image: copy union of overlay and manifest entries; skip identical files; cp -p to destinations; sudo for rootfs/*; set INITRD_DIRTY when kernel/Image or rootfs/modules are written.
- Mirror kernel Image into rootfs if kernel changed: copy kernel/Image to both bsp_image locations and mark INITRD_DIRTY.
- Refresh initramfs when INITRD_DIRTY=1 by running tools/l4t_update_initrd.sh in the bsp_image, which generates boot/initrd and related files.
- Summary and next step: report overlay/manifest scopes, counts, kernel/initramfs status, and point to /jetson-flash-image (or /jetson-validate-image for inspection).
When to use it
- As the first leg of Deploy: jetson-promote-image → jetson-flash-image → jetson-validate-image.
- Standalone to update bsp_image for inspection, out-of-band builds, or handing to a separate flashing host.
What it can touch
- Bsp image path: <bsp_image.root_path>/Linux_for_Tegra/
- Local source and manifest files: <source.root_path>/Linux_for_Tegra, <source.root_path>/.build-manifest.yaml, <source.root_path>/.build-state.yaml
- Tools: uses git, yq, cmp, sudo as part of the workflow.
Caveats
- Two channels share a single destination; manifest entries win on conflicts.
- Diff-aware copy is idempotent; re-run with no changes is a no-op.
- Kernel-image mirror and initramfs refresh occur only when relevant writes happen; requires tools/l4t_update_initrd.sh to exist in bsp_image.
- If a required path or tool is missing, it routes to initialization steps or reports issues per documented gates.
# Promote BSP Image ## Purpose Stage every Customize-* and Build output into `bsp_image` so it is ready for `/jetson-flash-image`. This is the **promote leg of Deploy** — it copies files, never flashes and never builds. ## Prerequisites - Active target-platform profile with both `source:` and `bsp_image:` resolved (run `/jetson-init-source` and `/jetson-init-image` first). - `<source.root_path>/Li
What does the jetson-promote-image skill do?
Use to promote overlay files and built artifacts into the staged BSP image. Do NOT use to flash or build. Triggers: promote bsp image.
How do I install it?
Run `npx skills add NVIDIA/skills --skill jetson-promote-image --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From NVIDIA/skills, a repository with 2,789 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.