What problem does it solve? Reporting bugs, requesting features, or disclosing vulnerabilities for swamp and its extensions normally requires knowing where each report should go and how to format it. This Skill routes reports to the swamp.club Lab, an extension publisher's repository, or email, and handles follow-up comments and issue status changes through the swamp CLI. ## Core Features & Use Cases - Issue retrieval and submission: Fetch issue details with swamp issue get, and file bug reports, feature requests, or security disclosures with interactive or non-interactive commands. - Extension-scoped routing: Use --extension @collective/name to route reports to @swamp/* Lab issues or third-party publisher repositories via gh or browser handoff, with clean refusals when no repo exists. - Ripples and status changes: Post comments on existing Lab issues with swamp issue ripple, optionally closing or reopening the issue in the same flow. - Use Case: You discover the @swamp/aws-ec2 extension returns empty attributes for stopped instances. The Skill checks whether the bug is already fixed in a newer version, then files a tagged Lab issue with reproduction steps and environment details. ## Quick Start Ask the assistant to file a bug report against swamp describing the problem, reproduction steps, and environment, and it will run the appropriate swamp issue command and return the issue number and URL.
