What problem does it solve? Turning loose todos, memos, and bug reports into well-structured GitHub Issues requires manual fact-checking, template selection, and label assignment, which often results in vague or inaccurate issues. ## Core Features & Use Cases - Claim Verification: Extracts verifiable claims from your draft and checks them against the repository (Glob/Grep/Read, git log/blame) and official external docs before writing anything. - Automatic Classification: Selects the right issue type (bug report, feature request, task, test, research) and matching labels from the repository's existing label set. - Duplicate Detection: Searches open and closed issues for related work and links them with Related to #N instead of creating duplicates. - Use Case: After a debugging session, ask to file a bug report; the Skill verifies the error path in code, picks the bug template, attaches verified references, and creates the issue after your approval. ## Quick Start Ask the assistant to turn the current conversation's findings into a GitHub issue, for example by saying "verify this bug report and create an issue for it".