bug

Name: bug
Availability: InStock
Author: pcortellezzi

Create structured GitHub issues with Expected/Observed sections and reproduction steps.

Updated Aug 23, 2026

Search Tags:#automation #github #issue #triage #reproduction #specs #bug

Ready to run

npx skills add https://github.com/pcortellezzi/rs_trader --skill bug-pcortellezzi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/pcortellezzi/rs_trader/tree/main/.claude/skills/bug
Command: npx skills add https://github.com/pcortellezzi/rs_trader --skill bug-pcortellezzi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a freeform bug description into a well-structured GitHub issue that clearly documents expected vs observed behavior, reproduction steps, related specifications, and severity, saving time during triage and ensuring consistent reports.

Core Features & Use Cases

Structured Issue Creation: Builds an issue body with Expected Behavior, Observed Behavior, Reproduction Steps, Related Specs, and Environment details.
Severity & Labeling: Determines whether the report is a regression or a new bug and applies the appropriate label.
Use Case: When a developer or tester reports an anomaly, use this Skill to generate a reproducible, discoverable GitHub issue that links to relevant spec IDs.

Quick Start

Create a GitHub issue describing the observed vs expected behavior, reproduction steps, and any related spec IDs.

Frequently Asked Questions about bug

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

FAQPage Schema

How do I create structured GitHub bug reports from a freeform description?▼

To create structured GitHub bug reports, provide a freeform description of the anomaly. The tool generates an issue body containing Expected Behavior, Observed Behavior, Reproduction Steps, Related Specs, and Environment details for clear triage.

What is the best way to document expected versus observed behavior for issue triage?▼

Documenting expected versus observed behavior for issue triage requires separating the anticipated outcome from the actual anomaly. This approach structures reports with clear sections, reproduction steps, and related spec identifiers to ensure discoverability.

Can I automatically apply bug or regression labels when creating GitHub issues?▼

You can automatically apply bug or regression labels when creating GitHub issues. The tool determines whether the reported anomaly is a new bug or a regression, applying the appropriate label to streamline developer triage.

How do I include related spec identifiers in a GitHub issue report?▼

To include related spec identifiers in a GitHub issue report, reference the specific specification IDs within your freeform description. The generated issue links these spec IDs alongside the observed behavior and reproduction steps.

Does this bug report generator work with CLI or API tooling for GitHub?▼

This bug report generator works with CLI or API tooling for GitHub. It generates structured issue content with clear Expected and Observed sections, reproduction steps, and related spec IDs for integration into developer workflows.