reporting-bugs

Transforms rough tester notes and evidence into reproducible, developer-ready defect reports.

113|17|Updated Oct 5, 2025
One-click install
npx skills add https://github.com/jaktestowac/awesome-copilot-for-testers --skill reporting-bugs-jaktestowac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reporting-bugs
Source: https://github.com/jaktestowac/awesome-copilot-for-testers/tree/main/plugins/reporting-bugs/skills/reporting-bugs
Command: npx skills add https://github.com/jaktestowac/awesome-copilot-for-testers --skill reporting-bugs-jaktestowac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Testers often capture bugs as scattered notes, screenshots, or console output that developers cannot act on. This Skill converts that raw material into structured, reproducible bug reports with clear severity, evidence, and follow-up guidance. ## Core Features & Use Cases - Structured Report Generation: Builds complete bug reports with title, environment, preconditions, numbered reproduction steps, actual vs expected results, and evidence lists using a standard template. - Severity & Confidence Classification: Grades issues by user or business impact using a severity matrix (Critical/High/Medium/Low) and tracks confidence and reproducibility levels. - Intermittent Issue Triage: Captures reproduction patterns (always, sometimes, seen once, not reproduced) for flaky or hard-to-reproduce defects. - Use Case: After an exploratory testing session, paste your rough notes and a screenshot, and receive a polished defect report ready to paste into Jira or your team's ticketing system. ## Quick Start Turn my rough testing notes and this screenshot into a complete bug report with severity and reproduction steps.

Frequently Asked Questions about reporting-bugs

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

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

A reproducible bug report needs a clear title, environment details, preconditions, numbered steps to reproduce, and explicit actual vs expected results. Attach evidence like screenshots, logs, or payloads so developers can verify the issue without extra back-and-forth.

How do I triage an intermittent or hard-to-reproduce bug?▼

Capture the reproduction pattern explicitly as always, sometimes, seen once, or not reproduced yet. Record environment details, timestamps, and any triggering conditions, and mark confidence as suspected rather than confirmed when reproduction is unreliable.

How should I assign severity to a software defect?▼

Grade severity by user or business impact, not frustration level. Critical means blocked core flows or data loss, High means a major feature broken with no workaround, Medium means a workaround exists, and Low covers minor or cosmetic issues.

What evidence should I attach to a bug report?▼

Attach screenshots, screen recordings, console or network logs, request payloads, and timestamps whenever available. Evidence should travel with the bug so developers can confirm the behavior without needing to recreate your exact setup first.

When should I avoid stating a root cause in a bug report?▼

Avoid stating root cause as fact when you lack confirming evidence, since speculation misleads developers. Place strong suspicions in a separate Notes or Hypothesis section, clearly separated from observed facts.