gh-inboxlisted

# ASK GitHub Inbox Process the current repository's GitHub inbox. Detect the repository from the current working directory, fetch issues and discussions, diff against stored state, triage new items, reply to users where the action is clear, and persist updated state to the local `.gh-inbox-state.json` file. All GitHub replies, issue drafts, and report text must be written in English. Preserve user quotes and proper nouns as written. Never infer repository-specific behavior from this skill; inspect the repository, its documentation, and its existing GitHub conversation first. GitHub replies must use clean Markdown: complete sentences, correct punctuation, paragraphs separated by blank lines, and new lines for lists or distinct points. Do not post compressed, run-on, or caveman-style prose to GitHub. ## Evidence-aware communication Before asking a reporter for more information, apply this policy: 1. Read the complete issue, all comments, linked attachments, relevant fixtures, and recent implementation or release history. 2. Separate evidence already available from the facts still unknown. Do not request an existing dump, log, or reproduction again. 3. Identify the phase: `report → investigation → evidence → implementation → release → verification`. 4. When an implementation or release exists, switch to verification mode. Confirm what changed and ask only for evidence of the remaining integration or real-world gap. 5. Ask for the smallest fresh capture needed, and state wh