What problem does it solve? Answering GitHub issues as a maintainer requires reading full threads, verifying technical claims against the actual code, and writing clear replies — a process that is easy to get wrong when done hastily. This Skill structures that workflow so nothing is published without verification and explicit approval. ## Core Features & Use Cases - Full thread fetching: Retrieves the issue body and every comment via gh issue view before briefing, avoiding summaries based on the title alone. - Code-verified answers: Checks technical claims against the real codebase (reading classes, counting call sites) before endorsing any external finding. - Approval-gated publishing: Drafts replies in plain B2-level English, shows them for review, and posts with gh issue comment only after explicit user approval. - Use Case: A maintainer returns to a repository with five open issue discussions. The Skill walks through each one — briefing the thread, verifying claims against the code, drafting the reply, and publishing only after sign-off — then records the outcome in persistent memory. ## Quick Start Reply to GitHub issue #42: fetch the thread, brief me on the open questions, verify the technical claims against the code, and draft a response for my approval.
