mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- mcore-create-issue
- license
- Apache-2.0
- argument
- GitHub Actions run or job URL
- metadata
- { "author": "Philip Petrakian <ppetrakian@nvidia.com>" }
- description
- Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
- 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 failure'.
- user_invocable
- true
02 资源文件 4
- 参考文档BENCHMARK.md2.8 KB
- 参考文档evals/evals.json3 B
- 参考文档skill-card.md2.4 KB
- 其他skill.oms.sig4.5 KB
03 SKILL.md 正文
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_idwas provided, use that job directly. -
If only a
run_idwas provided, list all failed jobs in the run: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:
# 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:
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:
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:
# 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:
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.
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:
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.
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:
**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.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.