skills.rest
wsman
wsmanCOMMUNITY
Explore all skills by this author →
GitHub

bug-report

Create structured bug reports from incident descriptions or source-code analysis.

18|5|Updated Nov 25, 2025
Search Tags:#code analysis#debugging#qa#verification#bug report#triage
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill bug-report-wsman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/bug-report
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill bug-report-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn vague bug descriptions or code observations into complete, review-ready bug reports with clear reproduction steps, severity, and context.

Core Features & Use Cases

  • Structured Bug Triage: Converts a user-described issue into a standardized report that includes summary, classification, environment, and expected versus actual behavior.
  • Code-Based Bug Analysis: Reviews a target file or path and identifies likely defects such as edge cases, state issues, and missing validation.
  • Fix Verification and Closure Workflow: Supports verification of a bug fix and produces a closure record once the issue is confirmed resolved.
  • Use Case: A QA analyst can paste a failure description or point to a suspicious file and quickly produce a report that developers can act on immediately.

Quick Start

Ask the bug-report skill to analyze the affected file or describe the issue you observed so it can generate a structured bug report.

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I create a structured bug report from a vague issue description?▼

To create a structured bug report, paste your incident description or code observation. The system converts it into a review-ready record with reproduction steps, severity, environment, and expected versus actual behavior.

Can I scan source code files to identify potential bugs and edge cases?▼

Yes, you can scan source code by pointing to a target file or path. The analysis identifies likely defects such as edge cases, state issues, and missing validation, turning them into actionable reports.

What is the best way to verify a bug fix and document the closure?▼

The best way to verify a bug fix is using the closure workflow. It supports fix verification and produces a closure record once the issue is confirmed resolved, capturing review-ready status with explicit approval gates.

Does the bug triage process require explicit approval before writing report files?▼

Yes, the bug triage process includes explicit approval gates before writing files. This ensures all generated reports and closure records are reviewed and confirmed before being committed to your software project.

How do I triage software defects for a QA team to make them actionable for developers?▼

To triage software defects for a QA team, input the failure description or suspicious file. The system generates a standardized report with classification and technical context that developers can act on immediately.

Related Skills

Explore More Software Engineering Skills→
Synthesys-LabSynthesys-Lab
56

Debugging Report

Diagnose failing tests and generate structured bug reports.

Official
Basic
HechaoYannetHechaoYannet

story-done

Verify story completion against acceptance criteria, ADR/GDD references, and DoD.

Community
Advanced
johnatas-henriquejohnatas-henrique

bug-report

Generate structured bug reports from user descriptions or static code analysis.

Community
Advanced
LeandroBenjaminLLeandroBenjaminL

sdd-archive

Automate SDD cycle closure by merging delta specifications into main project specifications.

Community
Advanced