report-bug

Name: report-bug
Availability: InStock
Author: the-rabak

Generates a formatted bug report for the compound-engineering plugin.

Updated Mar 3, 2026

Search Tags:#automation #debug #plugin #bug-report #compound-engineering #environment-info #reproduce-steps

Ready to run

npx skills add https://github.com/The-Rabak/naysmith --skill report-bug-the-rabak

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: report-bug
Source: https://github.com/The-Rabak/naysmith/tree/main/.github/skills/report-bug
Command: npx skills add https://github.com/The-Rabak/naysmith --skill report-bug-the-rabak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes and streamlines the process of reporting bugs for the compound-engineering plugin by guiding users to collect essential context and generate a ready-to-file report.

Core Features & Use Cases

Automates collection of plugin version, CLI tool versions, and OS information
Formats a comprehensive bug report with sections for description, environment, steps to reproduce, and error messages
Saves the report to a file and instructs the user where to file it (maintainer or repository)

Quick Start

Provide the bug details and run /report-bug to generate a complete bug report.

Frequently Asked Questions about report-bug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I structure a bug report for a plugin issue?▼

A standardized bug report requires environment data, steps to reproduce, and error messages. Formatting these details into a structured report file ensures maintainers can quickly reproduce and document the plugin issue across CLI, UI, and integrations.

What environment info do I need to include when reporting a bug?▼

Essential environment info for bug reporting includes the plugin version, CLI tool versions, and OS information. Automating the collection of this environment data ensures the bug report provides maintainers with the necessary details to reproduce the issue accurately.

Can I use this approach to document bugs across CLI and UI interactions?▼

Yes, this bug reporting approach applies to CLI, UI interactions, and integrations. The standardized guidance enforces a structured report format that helps you reproduce and document issues consistently regardless of the interface you are using.

What's the best way to automate collecting steps to reproduce a bug?▼

The best way to automate collecting steps to reproduce a bug is to generate a comprehensive report with dedicated sections for description, environment, and reproduction steps. This standardizes the reproduction details and saves them directly to a structured file artifact.

Where do I file a bug report after generating it?▼

After generating a bug report, you should file it with the maintainer or repository. The bug reporting process saves the standardized report to a file and instructs you exactly where to submit the document for the compound-engineering plugin.