Bug Capture

When a user casually mentions something broken during testing or says "file an issue," this skill turns the conversation into a properly structured GitHub issue written in your project's own vocabulary. It asks one or two clarifying questions, explores the codebase in parallel to learn domain terms, checks for duplicates, then files directly without making you review a draft. The clever part is the anti-staleness rule: no file paths, no line numbers, no function names. Just behavior described in the language your team already uses, so the issue still makes sense after a refactor. It knows when to file one issue versus breaking a report into multiple blocked children.