report-bug

Collect bug details and create formatted GitHub issues via GitHub CLI.

1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/JimmyChen-NXP/zephyr-team-activity-dashboard --skill report-bug-jimmychen-nxp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-bug
Source: https://github.com/JimmyChen-NXP/zephyr-team-activity-dashboard/tree/main/.github/skills/report-bug
Command: npx skills add https://github.com/JimmyChen-NXP/zephyr-team-activity-dashboard --skill report-bug-jimmychen-nxp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of reporting bugs encountered in the compound-engineering plugin by gathering necessary technical details and automatically creating a GitHub issue.

Core Features & Use Cases

  • Structured Bug Reporting: Collects essential information like bug category, component, actual/expected behavior, reproduction steps, and error messages.
  • Environment Data Collection: Automatically gathers plugin version, Claude Code version, and OS information.
  • Automated Issue Creation: Uses the GitHub CLI to create a well-formatted issue in the specified repository.
  • Use Case: A user encounters an issue where a specific command within the compound-engineering plugin fails. They use this skill to report the bug, providing all necessary details for the maintainer to diagnose and fix the problem efficiently.

Quick Start

Use the report-bug skill to report an issue you are experiencing with the compound-engineering plugin.

Frequently Asked Questions about report-bug

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

FAQPage Schema
How do I report a bug in the compound-engineering plugin?

To report a compound-engineering plugin bug, use this skill to collect details like reproduction steps and system information, then automatically generate a structured GitHub issue. It streamlines the troubleshooting process by formatting the report with relevant labels for maintainers.

Do I need GitHub CLI installed to submit a bug report?

Yes, GitHub CLI is required to submit a bug report. The skill relies on the GitHub CLI to automate the creation of well-formatted issues in the specified repository, ensuring the bug report is properly submitted with structured formatting and relevant labels.

What information is needed to create a GitHub issue for a plugin bug?

Creating a GitHub issue requires the bug category, affected component, actual and expected behavior, reproduction steps, and error messages. The skill also automatically retrieves environment data like plugin version, Claude Code version, and OS information to complete the report.

Can I automatically gather environment data when troubleshooting a plugin issue?

Yes, you can automatically gather environment data when troubleshooting a plugin issue. The skill executes specific shell commands to retrieve the plugin version, Claude Code version, and OS information, appending this technical context to the GitHub issue automatically.

What is the best way to structure a bug report for a Claude Code plugin?

The best way to structure a bug report is by using an automated skill to format the GitHub issue. It organizes user-provided details like actual versus expected behavior and reproduction steps into a standardized layout with relevant labels for the compound-engineering repository.

Why does my bug report skill fail to submit an issue to GitHub?

The bug report skill may fail to submit an issue if the GitHub CLI is not installed or authenticated. It depends on the GitHub CLI to push the structured bug report and environment data to the repository, requiring proper command-line access.