report-bug-ce

To report a bug for the compound-engineering plugin, use a guided skill that collects structured details like reproduction steps and error messages, then automatically creates a standardized GitHub issue in the official repository.

Creating a structured GitHub issue for an OpenClaw plugin error involves gathering the bug category, affected component, and actual versus expected behavior, which the skill formats automatically into a standardized report for maintainers.

Yes, the bug reporting skill automatically gathers environment metadata, including OS information, plugin version, and agent CLI version, without requiring manual input from the user.

If your compound-engineering plugin command crashes unexpectedly, you should use the bug reporting skill to quickly capture all relevant details and submit a complete, actionable report to the maintainer without manual formatting.

Yes, you can use this skill to report issues with MCP servers, installation processes, agents, skills, or plugin commands, as it guides you through providing all required details for any of these components.

When submitting a plugin troubleshooting report, the required information includes the bug category, affected component, actual and expected behavior, reproduction steps, and error messages to ensure the issue is actionable.