GitHub Issue Repro And Fix

Use this skill when the user provides a GitHub issue URL, issue number, copied issue body, or asks whether reported behavior is truly a bug before fixing it.

Workflow

1. Gather the issue context.

   • If given a URL or issue number, prefer gh issue view <number> --json title,body,comments,labels,author,state,url.
   • If gh is unavailable or unauthenticated, use the GitHub web page or ask the user only when the issue content cannot be accessed.
   • Read the issue comments, not just the opening report. Comments often contain maintainer guidance, reproductions, workarounds, duplicate links, and notes that the issue was fixed elsewhere.
   • Capture the exact reported behavior, expected behavior, environment, reproduction steps, linked repro repository or sandbox, maintainer comments, and any user-confirmed workarounds.

2. Look for related upstream context.

   • Search repository issues, pull requests, and discussions for the issue number, mentioned APIs, error text, and reproduction keywords.
   • Prefer GitHub search or gh search issues/gh search prs when available.
   • Note related PRs, discussions, duplicate issues, regression reports, and changelog entries before deciding whether to patch.
   • If a related PR already fixed the issue, verify whether the local workspace contains that change before editing.