skills.rest
xiduzo
xiduzoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

wtf.report-bug

Create GitHub Bug issues linked to originating Task and Feature.

7|2|Updated Apr 8, 2026
Search Tags:#github#qa#gherkin#issue-management#bug-report#task-feature-link
One-click install
npx skills add https://github.com/xiduzo/wtf --skill wtf-report-bug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wtf.report-bug
Source: https://github.com/xiduzo/wtf/tree/main/skills/wtf.report-bug
Command: npx skills add https://github.com/xiduzo/wtf --skill wtf-report-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables developers and QA engineers to quickly file a structured GitHub Bug issue from a QA finding. It links the bug to the originating Task and Feature, maps failing Gherkin scenarios as reproducible evidence, and ensures every section of the BUG template is populated for traceability and quick triage.

Core Features & Use Cases

  • Link a Bug to the originating Task and Feature to preserve context across the lifecycle.
  • Map failing Gherkin scenarios to reproducible evidence and align with the BUG template.
  • Draft and file a standardized bug report in GitHub, optionally attaching reproduction steps, observed vs. expected behavior, and contracts.
  • Support fast-path bug filing from a hotfix workflow by focusing on essential sections and auto-linking artifacts.
  • Create comments on the originating Task/Feature to notify stakeholders of the new bug.

Quick Start

Summarize the observed failure, link to the relevant Task and Feature, and invoke the wtf.report-bug skill to file a structured GitHub Bug issue.

Frequently Asked Questions about wtf.report-bug

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

FAQPage Schema
How do I create a structured GitHub bug report from failed Gherkin scenarios?▼

To create a structured GitHub bug report from failed Gherkin scenarios, summarize the observed failure and link the relevant Task and Feature. The skill automates drafting a standardized issue using your repo's BUG template, mapping the failing scenarios as reproducible evidence.

What is the best way to link a GitHub bug issue to its originating Task and Feature?▼

Linking a GitHub bug issue to its originating Task and Feature preserves context across the lifecycle. This skill automates the linkage during bug report creation and posts comments on the originating artifacts to notify stakeholders of the new defect.

How do I file a bug report that includes observed vs expected behavior and reproduction steps?▼

Filing a bug report with observed vs expected behavior and reproduction steps requires gathering the failure details and invoking the skill. It applies a guided process to collect contracts and suggested fixes, then drafts the standardized GitHub issue.

Can I file a fast-path bug report from a hotfix workflow?▼

Yes, you can file a fast-path bug report from a hotfix workflow. The skill supports this by focusing on essential template sections and auto-linking artifacts, allowing developers to quickly file a structured GitHub Bug issue during urgent fixes.

Does this skill require a specific GitHub bug issue template to function?▼

The skill drafts a standardized bug report using the repository's BUG template to ensure every section is populated for traceability and quick triage. It populates sections like observed vs expected behavior, reproduction steps, and contracts based on this template.

Why should I use a structured bug reporting process instead of manually creating GitHub issues?▼

A structured bug reporting process ensures every section of the BUG template is populated for traceability and quick triage. It automates mapping failing Gherkin scenarios as reproducible evidence and links the bug to the originating Task and Feature, preventing manual context loss.

Related Skills

Explore More Software Engineering Skills→
tan-yong-shengtan-yong-sheng
1

gstack-qa-only

Generate structured QA reports with health scores, screenshots, and reproduction steps.

Community
Advanced
ric03uecric03uec
49

itx:bug-update

Verify GitHub issue labels and post structured comments with context logs.

Community
Basic
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
DMokongDMokong

spec-create

Create a formal spec.md and isolated Git worktree for new features.

Community
Advanced