skills.rest
heaptracetechnology
heaptracetechnologyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bug-report

Create structured bug reports with reproduction steps and expected versus actual results.

13|3|Updated Mar 27, 2026
Search Tags:#qa#environment#evidence#reproduce#report#severity#bug
One-click install
npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill bug-report-heaptracetechnology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/qa/bug-report
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill bug-report-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides QA engineers to craft clear, structured bug reports that shorten debugging time by detailing reproducible steps, expected vs. actual behavior, environment data, and root-cause hypotheses.

Core Features & Use Cases

  • Structured templates that capture steps, conditions, and observations for consistent bug reporting.
  • Evidence-first reporting with sections for screenshots, logs, and network traces to accelerate debugging.
  • Severity and priority guidance to help triage noisy backlogs and align fixes with impact.
  • Reproducibility-focused workflow that documents minimal steps and known workarounds.
  • Templates and checklists to communicate effectively with developers and stakeholders.

Quick Start

Describe a bug scenario and run the skill to generate a complete, submission-ready report.

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I write a bug report that developers can actually reproduce?▼

To write a reproducible bug report, document minimal steps to reproduce, expected versus actual results, and environment metadata. Structured templates ensure consistent evidence capture like screenshots and logs to accelerate debugging.

What should be included in QA testing bug reports for web and mobile applications?▼

QA testing bug reports should include environment metadata, evidence like network traces, severity classification, and root-cause hypotheses. Capturing observations and known workarounds helps triage noisy backlogs and align fixes with impact.

How do I classify bug severity and priority during incident triage?▼

Classify bug severity and priority during incident triage by aligning fixes with user impact. Standardized templates guide severity classification and reproducibility-focused workflows to help developers and stakeholders communicate effectively.

Can I use a structured template for user-reported issues and incident triage?▼

Yes, you can use structured templates for user-reported issues and incident triage. Templates enforce evidence-first reporting with sections for logs and network traces, ensuring submission-ready documentation across project teams.

What is the best way to document environment metadata and evidence for bug reports?▼

The best way to document environment metadata and evidence is using an evidence-first reporting workflow. Capture screenshots, logs, and network traces alongside reproducibility conditions to shorten debugging time and guide developers.

Why does my bug report lack enough detail for developers to find the root cause?▼

Your bug report lacks detail if it misses root-cause prompts, environment data, or expected versus actual behavior. Structured templates enforce evidence capture and minimal reproducible steps to guide developers toward fixes.

Related Skills

Explore More Software Engineering Skills→
TheBushidoCollectiveTheBushidoCollective
187

debugging

Diagnose software bugs through evidence collection and hypothesis testing.

Official
Advanced
causify-aicausify-ai
144

github.triage_bug

Analyzes GitHub issues to determine status, root cause, difficulty and suggested actions.

Official
Basic
Nuwanda04Nuwanda04

Incident Commander

Classify technology incidents into SEV1-SEV4 and generate response communications.

Community
Advanced
TheBushidoCollectiveTheBushidoCollective
187

sre-incident-response

Manage production incidents across detection, triage, mitigation, and postmortem workflows.

Official
Intermediate