respond-to-issue

To draft a GitHub issue response, extract the issue context and research the relevant Megatron-LM code and recent commits. This produces a concise, fact-checked maintainer-ready comment that verifies claims with git data and includes next steps.

The best way to triage external bug reports is to pull the issue title, body, comments, and labels to classify the report, then search the codebase and check recent history to confirm what changed and why.

You can fact-check technical claims by verifying details against repository history using git and gh data. This confirms expected behavior, points to relevant implementation paths, and ensures the response contains evidence-based guidance rather than guesses.

Yes, this approach works for bug reports, feature requests, and contributor questions that require evidence-based guidance. It determines the issue type from labels and comments, then drafts a professional response with workarounds or patch directions.

You need to provide the issue URL or issue number. The process then drafts a GitHub reply by verifying details against the repository history and suggesting appropriate workarounds or follow-up actions.