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-LM CI Failure Triage

by NVIDIA in NVIDIA/Megatron-LM

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.

OfficialApache-2.0Auto-check passedDevOps & Cloud

Install Megatron-LM CI Failure Triage

skills CLI
$ npx skills add NVIDIA/Megatron-LM --skill mcore-create-issue -a claude-code

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

GitHub CLI
$ gh skill install NVIDIA/Megatron-LM mcore-create-issue --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/mcore-create-issue .claude/skills/mcore-create-issue && 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
mcore-create-issue
GitHub stars
18k
Token cost
~1.6k tokens
SKILL.md length
396 words
Files
5
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

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.

  • Works in 7 steps: Parse the URL → Identify failed jobs → Fetch the failure logs → …
  • A Megatron-LM CI job failed and needs a bug issue
  • Calls gh and pytest; reaches github.com
  • Tracing a failed Actions run back to its pull request and test author

What it does

You pass a GitHub Actions job or run URL. The agent pulls out the run and job ids, lists the failed jobs when only a run was given (asking which to triage if several failed), and fetches the logs with the gh CLI, narrowing them to error lines such as FAILED, Traceback and assertion failures. If the filtered output is thin, it downloads the full logs and looks for the pytest failures section or the last non-zero exit.

It then resolves the triggering pull request from the run's head branch, which follows a pull-request/number pattern, and finds who last touched the failing test file by checking the PR's base branch, falling back to the PR's commits when the PR itself introduced the file. The result is a bug issue against NVIDIA/Megatron-LM. The skill ships with an evals file, a benchmark note and a skill card.

When your agent uses it

  • A Megatron-LM CI job failed and needs a bug issue
  • Tracing a failed Actions run back to its pull request and test author
  • Triaging several failed jobs from one workflow run

Example prompts

  • “Triage the failed unit test job in the latest Megatron-LM pull-request run and file an issue.”
  • “Find out which PR broke the Actions run I just linked and who last edited the failing test.”

Requirements

  • The gh CLI authenticated with access to NVIDIA/Megatron-LM

Workflow steps

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

  1. Parse the URL
  2. Identify failed jobs
  3. Fetch the failure logs
  4. Resolve the triggering PR and test author
  5. Extract the root cause
  6. Check for duplicate issues
  7. Create the issue

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:

    • gh
    • pytest

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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-LM CI Failure Triage loads about 1.6k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 396 words of instructions outside code blocks.

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

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

The full file from NVIDIA/Megatron-LM at commit 486a126, republished under its Apache-2.0 licence (© NVIDIA). 396 words, ~1,588 tokens.

Download SKILL.mdSave it as .claude/skills/mcore-create-issue/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
mcore-create-issue
description
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
license
Apache-2.0
when_to_use
User shares a GitHub Actions URL and wants to file a bug report; 'create an issue for this failure', 'file a bug for this CI run', 'triage this GitHub Actions…
user_invocable
true
argument
GitHub Actions run or job URL
metadata.author
Oliver Koenig <okoenig@nvidia.com>

Triage CI Failure into a GitHub Issue

Investigate a failing GitHub Actions job, extract the root cause, and file a well-structured bug issue against NVIDIA/Megatron-LM.

Workflow

1. Parse the URL

The argument is a GitHub Actions URL. It will be one of:

  • Job URL: https://github.com/<owner>/<repo>/actions/runs/<run_id>/job/<job_id>
  • Run URL: https://github.com/<owner>/<repo>/actions/runs/<run_id>

Extract run_id and, if present, job_id.

2. Identify failed jobs

  • If a job_id was provided, use that job directly.

  • If only a run_id was provided, list all failed jobs in the run:

    bash
    gh run view <run_id> --repo NVIDIA/Megatron-LM --json jobs \
  --jq '[.jobs[] | select(.conclusion == "failure") | {id: .databaseId, name: .name, url: .url}]'

    If multiple jobs failed, ask the user which one to triage, or triage all of them if they say so.

3. Fetch the failure logs

For each failed job, retrieve the logs and narrow them down to the failure:

bash
# Pull the raw log and keep only error-bearing lines
gh api repos/NVIDIA/Megatron-LM/actions/jobs/<job_id>/logs 2>&1 \
  | grep -E "(FAILED|ERROR|\bError\b|assert|Traceback|Exception|##\[error\])" \
  | head -200

Also capture the full job name:

bash
gh run view --job <job_id> --repo NVIDIA/Megatron-LM --json name --jq .name

If the grep output is sparse, download the full logs and look for the pytest FAILURES section or the last non-zero exit signal.

4. Resolve the triggering PR and test author

Triggering PR: the run's head branch follows the pattern pull-request/<number>. Extract it and resolve the PR:

bash
gh run view <run_id> --repo NVIDIA/Megatron-LM --json headBranch --jq .headBranch
# → e.g. "pull-request/4332"
# Extract PR number and fetch metadata:
gh pr view <pr_number> --repo NVIDIA/Megatron-LM --json number,title,url \
  --jq '{number: .number, title: .title, url: .url}'

Test file author: find the GitHub login of whoever last touched the failing test file. The file may not exist on main — first determine the PR's base branch, then search from there:

bash
# 1. Get the PR's base branch (e.g. "main", "dev", "release/X.Y")
gh pr view <pr_number> --repo NVIDIA/Megatron-LM --json baseRefName --jq .baseRefName

# 2. Search commits on that base branch
gh api "repos/NVIDIA/Megatron-LM/commits?path=<test-file-path>&sha=<base-branch>&per_page=1" \
  --jq '.[0] | {login: .author.login, name: .commit.author.name, sha: .sha}'

If the result is empty (file was introduced by the PR itself), query the PR's commits instead:

bash
gh api "repos/NVIDIA/Megatron-LM/pulls/<pr_number>/commits" \
  --jq '[.[] | select(.files? // [] | any(.filename == "<test-file-path>"))] | .[0].author.login'

As a last resort, list the PR commits and pick the author of the commit whose message most closely relates to the failing test file.

Show full SKILL.md (150 more words)Show less
5. Extract the root cause

From the logs, identify:

  • Failed test(s): lines matching FAILED tests/...::... give the exact pytest node IDs.
  • Error message: the assertion failure, exception type, or first meaningful traceback frame — keep it under ~30 lines.
  • Job name: the GitHub Actions job name (e.g. tests/unit_tests/transformer/moe/**/*.py - latest).
  • Run / job URLs and PR URL: for linking in the issue.
6. Check for duplicate issues

Search for open issues that already cover the same test:

bash
gh issue list --repo NVIDIA/Megatron-LM \
  --state open \
  --search "<failed-test-filename>" \
  --json number,title,url \
  --limit 10
  • If a matching open issue exists, do not create a new one. Report the existing issue to the user and stop.
  • If no match is found, proceed to file a new issue.
7. Create the issue

Pass --assignee <test-author-login> to assign the issue to the test file's author. Include the triggering PR URL in the issue body.

bash
gh issue create \
  --repo NVIDIA/Megatron-LM \
  --title "🐛 CI failure: <failed-test-node-id>" \
  --label "bug" \
  --assignee "<test-author-login>" \
  --body "..."

Use the bug-report template body structure:

markdown
**Describe the bug**

CI test `<failed-test-node-id>` failed in job [`<job-name>`](<job-url>).
Tag @NVIDIA/mcore-oncall to get oncall's attention to this issue.

**Failing run**

| Field | Value |
|-------|-------|
| PR    | [#<pr_number>: <pr_title>](<pr_url>) |
| Run   | [<run_id>](<run_url>) |
| Job   | [<job_name>](<job_url>) |

**Error**

<core error message / traceback — 30 lines max>


**Steps/Code to reproduce bug**

Re-run the failing CI job linked above, or locally inside the dev container:

```bash
pytest <failed-test-node-id>

Additional context

Triaged automatically via /triage-issue.


If multiple tests failed in the same job, list each one as a separate bullet
under "Describe the bug" and include the combined error snippets. Assign the
issue to the author of whichever test file appears first in the failure list.

### 8. Report back to the user

Print the URL of the newly created issue (or the duplicate, if found) so the
user can review or share it.

## Important guidelines

- Never create an issue if a duplicate already exists — link the existing one instead.
- Always include the triggering PR link in the issue body.
- Always assign the issue to the test file's most recent author. If the author
  lookup fails (e.g. the commit was made by a bot or the login is unavailable),
  skip `--assignee` and note it in the "Additional context" section.
- Keep the error snippet concise (≤30 lines). Truncate long tracebacks and note that the full log is available via the job URL.
- Do not guess the root cause — quote the actual log output verbatim.
- If the job is still in progress or the logs are unavailable, say so and ask the user to retry once the run completes.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files in skills/mcore-create-issue of NVIDIA/Megatron-LM.

  • SKILL.md
  • BENCHMARK.md
  • evals/evals.json
  • skill-card.md
  • skill.oms.sig

Open the folder on GitHubat commit 486a126

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in NVIDIA/Megatron-LM, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Megatron-LM CI Failure Triage 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-LM CI Failure Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Megatron-LM CI Failure Triage this skillNVIDIA/Megatron-LM18k—~1.6kAutomated safety check: PassApache-2.0
GreptimeDB Fuzz CI Failure InvestigationGreptimeTeam/greptimedb6.7k—~4.4kAutomated safety check: PassApache-2.0
CI Failure Triage and RepairChachamaru127/claude-code-harness3.2k1 repos~1.1kAutomated safety check: NotesMIT
CI Watchdoglatitude-dev/latitude-llm4.7k—~1.6kAutomated safety check: PassMIT
Parallel CI Triagespencerpauly/awesome-cursor-skills841—~793Automated safety check: PassCC0-1.0
Gh Fix CIJetBrains/skills3637 repos~953Automated safety check: PassApache-2.0

Similar skills

  • GreptimeDB Fuzz CI Failure Investigation

    GreptimeTeam/greptimedb

    Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.

    6.7k GitHub stars~4.4k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • CI Failure Triage and Repair

    Chachamaru127/claude-code-harness

    Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.

    3.2k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check: notes

  • CI Watchdog

    latitude-dev/latitude-llm

    Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.

    4.7k GitHub stars~1.6k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Parallel CI Triage

    spencerpauly/awesome-cursor-skills

    When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel.

    841 GitHub stars~793 tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • Gh Fix CI

    JetBrains/skills

    Official

    A skill your agent uses when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and…

    363 GitHub starsUsed in 7 repos~953 tokens
    DevOps & CloudAuto-check passed

  • Openai Gh Fix CI

    trailofbits/skills-curated

    Official

    A skill your agent uses when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and…

    512 GitHub stars~955 tokensUpdated 2 mo ago
    DevOps & CloudAuto-check: notes

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

  • Megatron GB200 One-Node Test Onboarding

    NVIDIA/Megatron-LM

    Official

    Creates one-node GitHub merge-request variants of existing two-node GB200 functional tests in Megatron-LM, adjusting parallelism settings to fit four GPUs.

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

Works with

Categories

Questions about Megatron-LM CI Failure Triage

What does Megatron-LM CI Failure Triage do?

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. You pass a GitHub Actions job or run URL. The agent pulls out the run and job ids, lists the failed jobs when only a run was given (asking which to triage if several failed), and fetches the logs with the gh CLI, narrowing them to error lines such as FAILED, Traceback and assertion failures.

When should I use Megatron-LM CI Failure Triage?

Megatron-LM CI Failure Triage fits situations like: A Megatron-LM CI job failed and needs a bug issue; tracing a failed Actions run back to its pull request and test author; triaging several failed jobs from one workflow run.

How do I install Megatron-LM CI Failure Triage in Claude Code?

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

How do I install Megatron-LM CI Failure Triage in Codex?

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

Can I use Megatron-LM CI Failure Triage 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 mcore-create-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcore-create-issue, .gemini/skills/mcore-create-issue, .github/skills/mcore-create-issue and .opencode/skills/mcore-create-issue in your project.

What does Megatron-LM CI Failure Triage need to run?

Going by SKILL.md and its folder, Megatron-LM CI Failure Triage needs the command-line tools its instructions call (gh and pytest). Our summary lists: The gh CLI authenticated with access to NVIDIA/Megatron-LM.

Does Megatron-LM CI Failure Triage access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Megatron-LM CI Failure Triage 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-LM CI Failure Triage use?

Megatron-LM CI Failure Triage is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Megatron-LM CI Failure Triage use?

About 1.6k tokens (SKILL.md is roughly 6.4k 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-LM CI Failure Triage?

Skills that share tags, products or a category with Megatron-LM CI Failure Triage: GreptimeDB Fuzz CI Failure Investigation (GreptimeTeam/greptimedb, 6.7k stars), CI Failure Triage and Repair (Chachamaru127/claude-code-harness, 3.2k stars), CI Watchdog (latitude-dev/latitude-llm, 4.7k stars) and Parallel CI Triage (spencerpauly/awesome-cursor-skills, 841 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Megatron-LM CI Failure Triage?

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.