Mcore Linting And Formatting

nvidia/mcore-linting-and-formatting

Linting and formatting for Megatron-LM. Covers running autoformat.sh, tools (ruff, black, isort, pylint, mypy), and code style rules.

3k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

17319

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/NVIDIA/skills --skill mcore-linting-and-formatting

What comes with it

10 059 bytes besides the instruction

BENCHMARK.md

evals/evals.json

skill-card.md

skill.oms.sig

What it tells the agent to use

found in the instruction text

Bash runs shell commands — read the instruction before connecting

The instruction itself

5 sections, as written by the author

Linting and Formatting

Running the Formatter

Run before opening a PR:

# Check mode (no changes applied)
BASE_REF=main CHECK_ONLY=true SKIP_DOCS=false bash tools/autoformat.sh

# Fix mode
BASE_REF=main CHECK_ONLY=false bash tools/autoformat.sh

Tools invoked: black, isort, pylint, ruff, mypy.

Import Ordering

After editing imports in any Python files, always run uv run isort on those

files before committing:

uv run isort <file1>.py <file2>.py

Setting Up the Linting Group

Inside the container:

uv sync --locked --only-group linting

This installs ruff, black, isort, pylint — the same tools used by

tools/autoformat.sh and CI's linting job.

Code Style Rules

Type hints: required on all public API functions. Use X | None, not Optional[X].
Docstrings: Google-style on all public classes and functions.
Naming: follow Python conventions — snake_case for functions and variables, PascalCase for classes.
Line length: 119 characters (configured in pyproject.toml).
No bare except: always catch specific exception types.

How to use it

Copy the folder

Take nvidia/mcore-linting-and-formatting from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.