What problem does it solve? User-reported bugs in GitHub Discussions require multi-turn investigation — verifying claims against source code, asking clarifying questions, and routing confirmed bugs to the right engineer — which is tedious to do manually on a recurring cadence. ## Core Features & Use Cases - Automated bug triage: Scans the GitHub Discussions Bugs category via the GraphQL API, applies moderation and engagement guards, and tracks per-thread investigation state across ticks. - Code-level verification: Traces reported behavior through the codebase using grep, git blame, git log, and test inspection to confirm or refute bug claims before replying. - Team routing: Queues confirmed bugs in a shared memory file for a dispatcher agent and escalates recurring user misconceptions to the docs owner. - Use Case: A user posts "ww send returns the wrong session id" in the Bugs category; the skill traces the command handler, confirms the regression against a recent commit, replies to the reporter, and queues the bug for the engineering peer. ## Quick Start Ask the agent to check bugs in the GitHub Discussions Bugs category and investigate any new reports.