verify-issue

Context

Repository: !gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "unknown" Default branch: !git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@refs/remotes/origin/@@' || echo main

Instructions

Verify a GitHub issue against the current codebase. Execute immediately without asking.

Match verification depth to what the conclusion rests on; escalate past reading when it hinges on runtime behavior, an environment difference, a third-party API's real shape, or a flaw in the issue's own reasoning.

Process

1. Fetch issue: Run gh issue view $ISSUE_NUMBER --json title,body,labels,state,author,comments ($ARGUMENTS is an issue number like 3766 or a full GitHub issue URL). Extract the title, body, every technical claim, and the issue's own proposed conclusion or fix. Download and read image attachments from the body when they carry the evidence (a screenshot often is the claim); when the evidence lives in a video or an attachment that cannot be read, say so instead of silently judging without it.

2. Decompose into claims, and find the load-bearing one: Sort each claim into the bucket that determines how it's verified:

   • Codebase claim, about how a specific file, function, type, or behavior works. Verify by reading the code.
   • Scope claim, about what is or isn't handled anywhere in the project. Verify by full-repo search, not just the named file.
   • External claim, about web standards, ARIA specs, third-party library behavior, runtime APIs, or browser conventions. Verify against authoritative sources and judge how load-bearing the claim is.