respond-to-issue

To draft a GitHub issue response that is technically grounded, use the respond-to-issue skill to fetch issue details via GitHub CLI, research the Megatron-LM codebase, verify cited specifics with git history, and format the reply as a quoted Markdown block for maintainer approval.

The best way to triage external bug reports and feature requests is to pull the full issue thread context, locate relevant source locations, and verify claims using git log and git show before drafting a contributor-friendly response.

No, you cannot use this skill to automatically post replies. It produces a concise, copyable quoted Markdown block containing the drafted response for maintainer review, ensuring a human approves the message before it is shared.

Drafting maintainer responses requires access to the GitHub CLI to fetch issue details and a local Megatron-LM codebase to research source locations and verify claims using git history before generating the response draft.

To ensure cited code specifics are accurate when replying to developer questions, the skill verifies all claims by re-reading source lines and checking recent history via git show and git log before formatting the response.

A limitation of this automated issue triage is its strict focus on the Megatron-LM codebase, meaning codebase research and source verification are specialized for that repository rather than supporting arbitrary external codebases.