New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Megatron Nightly Main-to-Dev Sync

by NVIDIA in NVIDIA/Megatron-LM

Domain knowledge for the nightly workflow that merges Megatron-LM's main branch into dev, covering conflict handling, CI iteration, failure investigation and known issues.

OfficialCustom licenceAuto-check passedDevelopment

Install Megatron Nightly Main-to-Dev Sync

skills CLI
$ npx skills add NVIDIA/Megatron-LM --skill nightly-sync -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/Megatron-LM nightly-sync --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/Megatron-LM.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/nightly-sync .claude/skills/nightly-sync && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nightly-sync
GitHub stars
18k
Token cost
~8.5k tokens
SKILL.md length
3,583 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
Custom licence

At a glance

Domain knowledge for the nightly workflow that merges Megatron-LM's main branch into dev, covering conflict handling, CI iteration, failure investigation and known issues.

  • Works in 4 steps: Create the Sync Branch and Merge → Create the Draft PR → CI Iteration → …
  • Running or reviewing the nightly main-to-dev merge in Megatron-LM
  • SKILL.md covers Phase 1: Create the Sync…, Phase 2: Create the Draft PR, Phase 3: CI Iteration and Phase 4: Mark PR Ready —…, plus 1 more section
  • Calls git, gh and uv

What it does

This skill is read by the automated bot that runs the nightly main-to-dev sync for Megatron-LM, and it holds the knowledge needed to merge, resolve conflicts, iterate on CI and ship the PR. Phase 1 creates a sync branch from origin/dev and merges origin/main without editing the message, then resolves conflicts surgically: no global theirs strategy and no blanket checkout of main's files. Main's version is taken wholesale only for a listed set of override files or for a specific commit that deliberately removes dev-only code.

A section on squash-merge chain detection explains why chained dev PRs can conflict with a squashed commit on main. For each conflicted file the bot checks git log on dev for follow-up commits, favors dev's version where they exist, and uses git diff against origin/dev to spot removed or reverted code. Worked examples come from an earlier sync PR and involve the emerging optimizers and distributed optimizer files. The description also covers CI architecture, failure investigation and known issues.

When your agent uses it

  • Running or reviewing the nightly main-to-dev merge in Megatron-LM
  • Resolving merge conflicts without discarding dev-only additions
  • Checking a squash-merged PR chain for lost dev follow-up commits

Example prompts

  • “Create the sync branch from origin/dev, merge origin/main and list the conflicted files.”
  • “For each conflicted file, check whether dev has follow-up commits after the code main brings in.”
  • “Resolve this merge conflict without blanket-taking main's version.”

Requirements

  • A Megatron-LM checkout with origin/main and origin/dev branches

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Create the Sync Branch and Merge
  2. Create the Draft PR
  3. CI Iteration
  4. Mark PR Ready — Strict Gate

What it can do on your machine

Read from SKILL.md and the folder at commit 486a126. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh
    • uv
    • docker
    • bash
    • python
    • black

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, gh, uv and docker, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Megatron Nightly Main-to-Dev Sync loads about 8.5k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 3,583 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~8.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 3,583 words (~8,497 tokens).

“This skill is read by the automated sync bot during the nightly-sync-main-to-dev workflow. It contains all domain knowledge for merging main into dev, resolving conflicts, iterating on CI, and shipping the PR.”

— opening of SKILL.md by NVIDIA, Custom licence
name
nightly-sync
when_to_use
Working on the nightly sync PR; investigating a nightly sync failure; resolving merge conflicts between main and dev; 'nightly sync failed', 'main-to-dev…

Read the full SKILL.md on GitHub

Files

Just SKILL.md in skills/nightly-sync of NVIDIA/Megatron-LM.

Open the folder on GitHubat commit 486a126

Compare with similar skills

Megatron Nightly Main-to-Dev Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Megatron Nightly Main-to-Dev Sync compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Megatron Nightly Main-to-Dev Sync this skillNVIDIA/Megatron-LM18k—~8.5kAutomated safety check: PassCustom licence
Worktrunk Release Workflowmax-sixty/worktrunk8.9k—~6.9kAutomated safety check: PassCustom licence
Git Conventionswerf/werf4.7k—~1.3kAutomated safety check: PassApache-2.0
Git Changes ReporterNo-Trade-No-Life/Yuan352—~1.2kAutomated safety check: PassMIT
Pypi ReleasealchemiststudiosDOTai/tunacode125—~2.2kAutomated safety check: PassMIT
npm Package Publisherklaudworks/universal-skills181—~923Automated safety check: PassMIT

Similar skills

  • Worktrunk Release Workflow

    max-sixty/worktrunk

    Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.

    8.9k GitHub stars~6.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Git Conventions

    werf/werf

    werf conventions for branch names and commit messages. An agent skill from werf/werf.

    4.7k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Git Changes Reporter

    No-Trade-No-Life/Yuan

    生成结构化 git 变更报告（JSON + Markdown）。使用此技能当用户提到"git 变更"、"commit 摘要"、"代码审查"、"release note"、"近期改动"、"每日摘要"，或需要分析指定 commit 区间的代码变更。包含三元组结构（设计意图、核心代码、影响范围）的语义化报告，适用于代码审查、发布说明、团队同步、CI/CD 等场景。

    352 GitHub stars~1.2k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

  • Pypi Release

    alchemiststudiosDOTai/tunacode

    This skill should be used when releasing tunacode-cli to PyPI.

    125 GitHub stars~2.2k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • npm Package Publisher

    klaudworks/universal-skills

    Releases an npm package by committing changes, bumping the version with npm version, pushing the tag and checking the GitHub Actions publish.

    181 GitHub stars~923 tokensUpdated 8 mo ago
    DevelopmentAuto-check passed

  • Release Lithoxyl

    mahmoud/lithoxyl

    Walks through releasing the lithoxyl Python package to PyPI: CalVer version bump, tagging, pushing and checking the published release.

    146 GitHub stars~1.3k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

More from NVIDIA/Megatron-LM

All 14 skills in this repo

  • Update Megatron Golden Values

    NVIDIA/Megatron-LM

    Official

    Refreshes stored golden values from a GitHub Actions run, reports signed percentage changes per model, and writes a summary ready for a pull request description.

    18k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Megatron-LM Container and Dependency Setup

    NVIDIA/Megatron-LM

    Official

    Walks an agent through working inside the Megatron-LM CI container and changing dependencies with uv, so lock files resolve the same locally and in CI.

    18k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Megatron-LM Base Image Bump

    NVIDIA/Megatron-LM

    Official

    Moves Megatron-LM CI to a newer NVIDIA PyTorch base image, updating both the GitHub and GitLab pins together and handling the CI follow-up.

    18k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Megatron-LM CI/CD Guide

    NVIDIA/Megatron-LM

    Official

    Explains Megatron-LM's CI pipeline, PR scope labels, triggering the internal GitLab CI with a dry run first, and investigating CI failures.

    18k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Megatron-LM CI Failure Triage

    NVIDIA/Megatron-LM

    Official

    Investigates a failing GitHub Actions run or job for Megatron-LM, finds the root cause plus the PR and test author involved, and files a structured bug issue.

    18k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Megatron GPT to Hybrid Migration

    NVIDIA/Megatron-LM

    Official

    Guides moving Megatron Core GPTModel checkpoints, configs, training commands and launch scripts to HybridModel, following the repository's migration document.

    18k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Megatron Nightly Main-to-Dev Sync

What does Megatron Nightly Main-to-Dev Sync do?

Domain knowledge for the nightly workflow that merges Megatron-LM's main branch into dev, covering conflict handling, CI iteration, failure investigation and known issues. This skill is read by the automated bot that runs the nightly main-to-dev sync for Megatron-LM, and it holds the knowledge needed to merge, resolve conflicts, iterate on CI and ship the PR. Phase 1 creates a sync branch from origin/dev and merges origin/main without editing the message, then resolves conflicts surgically: no global theirs strategy and no blanket checkout of main's files.

When should I use Megatron Nightly Main-to-Dev Sync?

Megatron Nightly Main-to-Dev Sync fits situations like: running or reviewing the nightly main-to-dev merge in Megatron-LM; resolving merge conflicts without discarding dev-only additions; checking a squash-merged PR chain for lost dev follow-up commits.

How do I install Megatron Nightly Main-to-Dev Sync in Claude Code?

Run `npx skills add NVIDIA/Megatron-LM --skill nightly-sync -a claude-code`. Or copy the skill folder (skills/nightly-sync in NVIDIA/Megatron-LM) into .claude/skills/nightly-sync in your project. Claude Code loads it when a task matches its description.

How do I install Megatron Nightly Main-to-Dev Sync in Codex?

Run `npx skills add NVIDIA/Megatron-LM --skill nightly-sync -a codex`. Or copy the skill folder (skills/nightly-sync in NVIDIA/Megatron-LM) into .agents/skills/nightly-sync in your project. Codex loads it when a task matches its description.

Can I use Megatron Nightly Main-to-Dev Sync in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/Megatron-LM --skill nightly-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nightly-sync, .gemini/skills/nightly-sync, .github/skills/nightly-sync and .opencode/skills/nightly-sync in your project.

What does Megatron Nightly Main-to-Dev Sync need to run?

Going by SKILL.md and its folder, Megatron Nightly Main-to-Dev Sync needs the command-line tools its instructions call (git, gh, uv, docker, bash and python). Our summary lists: A Megatron-LM checkout with origin/main and origin/dev branches.

Does Megatron Nightly Main-to-Dev Sync access the network?

SKILL.md contains no URLs. Its commands use git, gh, uv and docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Megatron Nightly Main-to-Dev Sync safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Megatron Nightly Main-to-Dev Sync use?

Megatron Nightly Main-to-Dev Sync has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Megatron Nightly Main-to-Dev Sync use?

About 8.5k tokens (SKILL.md is roughly 34k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Megatron Nightly Main-to-Dev Sync?

Skills that share tags, products or a category with Megatron Nightly Main-to-Dev Sync: Worktrunk Release Workflow (max-sixty/worktrunk, 8.9k stars), Git Conventions (werf/werf, 4.7k stars), Git Changes Reporter (No-Trade-No-Life/Yuan, 352 stars) and Pypi Release (alchemiststudiosDOTai/tunacode, 125 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Megatron Nightly Main-to-Dev Sync?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/Megatron-LM, which has 18,078 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.

Source: NVIDIA/Megatron-LM on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.