create-compelling-issues

An issue is a claim that work is needed. A weak one costs more than it saves — it lands in triage limbo, duplicates something closed last week, or points an agent at a bug that three commits already fixed. The tracker always lags the codebase. Prove the gap still exists before you file.

1. Search Before Filing

Search open and closed issues AND merged PRs. A recently fixed defect has a closed issue and a merged PR — and no open issue at all. Run at least two keyword sets: the symptom, and the file/function name.

R="$ORG/$REPO"
gh search issues --repo "$R" --limit 20 "<symptom keywords>"          # open + closed
gh search prs    --repo "$R" --merged --limit 20 "<symptom keywords>" # already shipped?
gh search issues --repo "$R" --match title --limit 20 "<file or function>"