Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Research and draft a response to a GitHub issue or question from an external contributor.
Install Respond To Issue
$ npx skills add NVIDIA/Megatron-LM --skill respond-to-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/Megatron-LM respond-to-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NVIDIA/Megatron-LM.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/respond-to-issue .claude/skills/respond-to-issue && rm -rf skills-srcUse ~/.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/
Install the "respond-to-issue" agent skill from https://github.com/NVIDIA/Megatron-LM/tree/main/skills/respond-to-issue into .claude/skills/respond-to-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-to-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NVIDIA/Megatron-LM/tree/main/skills/respond-to-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NVIDIA/Megatron-LM --skill respond-to-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/Megatron-LM respond-to-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/Megatron-LM.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/respond-to-issue .agents/skills/respond-to-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "respond-to-issue" agent skill from https://github.com/NVIDIA/Megatron-LM/tree/main/skills/respond-to-issue into .agents/skills/respond-to-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-to-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/Megatron-LM --skill respond-to-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/Megatron-LM respond-to-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/Megatron-LM.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/respond-to-issue .cursor/skills/respond-to-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "respond-to-issue" agent skill from https://github.com/NVIDIA/Megatron-LM/tree/main/skills/respond-to-issue into .cursor/skills/respond-to-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-to-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NVIDIA/Megatron-LM.git --path skills/respond-to-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NVIDIA/Megatron-LM --skill respond-to-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/Megatron-LM respond-to-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/Megatron-LM.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/respond-to-issue .gemini/skills/respond-to-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "respond-to-issue" agent skill from https://github.com/NVIDIA/Megatron-LM/tree/main/skills/respond-to-issue into .gemini/skills/respond-to-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-to-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NVIDIA/Megatron-LM respond-to-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NVIDIA/Megatron-LM --skill respond-to-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/Megatron-LM.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/respond-to-issue .github/skills/respond-to-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "respond-to-issue" agent skill from https://github.com/NVIDIA/Megatron-LM/tree/main/skills/respond-to-issue into .github/skills/respond-to-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-to-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/Megatron-LM --skill respond-to-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/Megatron-LM respond-to-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/Megatron-LM.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/respond-to-issue .opencode/skills/respond-to-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "respond-to-issue" agent skill from https://github.com/NVIDIA/Megatron-LM/tree/main/skills/respond-to-issue into .opencode/skills/respond-to-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-to-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
respond-to-issue- GitHub stars
- 18k
- Token cost
- ~915 tokens
- SKILL.md length
- 514 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Research and draft a response to a GitHub issue or question from an external contributor.
- Works in 6 steps: Understand the issue → Research the codebase → Verify before citing → …
- User shares a GitHub issue URL
- SKILL.md covers Workflow and Important guidelines
- Calls gh and git
What it does
Respond To Issue is an agent skill from NVIDIA/Megatron-LM, published by the product's own GitHub organization. Research and draft a response to a GitHub issue or question from an external contributor. Use when user shares a GitHub issue URL or asks to respond to a community question; 'respond to this issue', 'draft a reply', 'answer this GitHub question'. Takes a GitHub issue URL or number as its argument.
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with GitHub, NVIDIA AI Platform and Git. The repository describes itself as: Ongoing research training transformer models at scale.
When your agent uses it
- User shares a GitHub issue URL
- Asks to respond to a community question
- Respond to this issue
- Answer this GitHub question
Example prompts
- “respond to this issue”
- “draft a reply”
- “answer this GitHub question”
- “/respond-to-issue”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Understand the issue
- Research the codebase
- Verify before citing
- Draft the response
- Suggest follow-up actions
- Present to the maintainer
What it can do on your machine
Read from SKILL.md and the folder at commit eb50202. 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:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, 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
Respond To Issue loads about 915 tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 514 words of instructions outside code blocks.
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 514 words (~915 tokens).
“Help a maintainer draft a high-quality response to a GitHub issue from an external contributor.”
- name
- respond-to-issue
- user-invocable
- true
Files
Just SKILL.md in skills/respond-to-issue of NVIDIA/Megatron-LM.
Open the folder on GitHubat commit eb50202
Compare with similar skills
Respond To Issue 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Respond To Issue this skillNVIDIA/Megatron-LM | 18k | — | ~915 | Automated safety check: Pass | Custom licence | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Pull Request Title and Body Writeropeninterpreter/openinterpreter | 69k | 2 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| PR Review State Fetchprisma/orm | 48k | — | ~767 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
- Official
PR Review State Fetch
prisma/orm
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
More from NVIDIA/Megatron-LM
All 14 skills in this repo- Official
Megatron-LM Container and Dependency Setup
NVIDIA/Megatron-LM
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.
- Official
Megatron-LM Base Image Bump
NVIDIA/Megatron-LM
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.
- Official
Megatron-LM CI/CD Guide
NVIDIA/Megatron-LM
Explains Megatron-LM's CI pipeline, PR scope labels, triggering the internal GitLab CI with a dry run first, and investigating CI failures.
- Official
Megatron-LM CI Failure Triage
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.
- Official
Megatron GPT to Hybrid Migration
NVIDIA/Megatron-LM
Guides moving Megatron Core GPTModel checkpoints, configs, training commands and launch scripts to HybridModel, following the repository's migration document.
- Official
Megatron GB200 One-Node Test Onboarding
NVIDIA/Megatron-LM
Creates one-node GitHub merge-request variants of existing two-node GB200 functional tests in Megatron-LM, adjusting parallelism settings to fit four GPUs.
Related
Works with
Categories
Questions about Respond To Issue
What does Respond To Issue do?
Research and draft a response to a GitHub issue or question from an external contributor. Respond To Issue is an agent skill from NVIDIA/Megatron-LM, published by the product's own GitHub organization. Research and draft a response to a GitHub issue or question from an external contributor.
When should I use Respond To Issue?
Respond To Issue fits situations like: user shares a GitHub issue URL; asks to respond to a community question; respond to this issue; answer this GitHub question.
How do I install Respond To Issue in Claude Code?
Run `npx skills add NVIDIA/Megatron-LM --skill respond-to-issue -a claude-code`. Or copy the skill folder (skills/respond-to-issue in NVIDIA/Megatron-LM) into .claude/skills/respond-to-issue in your project. Claude Code loads it when a task matches its description.
How do I install Respond To Issue in Codex?
Run `npx skills add NVIDIA/Megatron-LM --skill respond-to-issue -a codex`. Or copy the skill folder (skills/respond-to-issue in NVIDIA/Megatron-LM) into .agents/skills/respond-to-issue in your project. Codex loads it when a task matches its description.
Can I use Respond To Issue 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 respond-to-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/respond-to-issue, .gemini/skills/respond-to-issue, .github/skills/respond-to-issue and .opencode/skills/respond-to-issue in your project.
What does Respond To Issue need to run?
Going by SKILL.md and its folder, Respond To Issue needs the command-line tools its instructions call (gh and git).
Does Respond To Issue access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Respond To Issue 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 Respond To Issue use?
Respond To Issue 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 Respond To Issue use?
About 915 tokens (SKILL.md is roughly 3.7k 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 Respond To Issue?
Skills that share tags, products or a category with Respond To Issue: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Respond To Issue?
NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/Megatron-LM, which has 18,094 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 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.