github-researchlisted

# GitHub Research ## Overview Collects evidence from GitHub: repos, code, issues, PRs, releases, discussions, commits. Each output is one evidence record — a claim backed by a verbatim quote pinned to a permanent anchor (commit SHA, not a branch that can move). This skill never concludes or synthesizes; it produces raw material for `state/runs/<slug>/evidence.jsonl`. **Layer rule:** produces evidence, not results. Synthesis and confidence status are the orchestrator's job. ## When to use Direct use: "find repos that do X", "what does the changelog say about Y", "check if this bug is still open". As a component: orchestrator dispatches this alongside web/reddit research for implementation-type claims. Don't use for: general web content (→ web-research), Reddit discussion even if it's about a GitHub project (→ reddit-research), writing/editing code in the current project (not a research task). ## Capability check (once per session, not per query) Run `gh auth status` first. Authenticated unlocks code search (unavailable anonymously — GitHub returns 401 with no anonymous mode, not a rate limit to route around) and higher limits. See references/tooling.md for the full chain and measured rate limits. ## Workflow 1. **Pick the right search surface** for the question: - Repo discovery → `gh search repos` (topic/stars/language filters) - "How is X implemented" → `gh search code` (auth required; returns `textMatches` — the verbatim quote, direct from the API) - "Is