skills.rest
cenconq25
cenconq25COMMUNITY
Explore all skills by this author →
GitHub

bug-report

Convert user descriptions, code samples, or crash logs into structured bug reports.

39|6|Updated May 3, 2026
Search Tags:#qa#triage#issue-tracking#bug-report#crash-log#repro-steps
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill bug-report-cenconq25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/bug-report
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill bug-report-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts vague QA notes, user reports, or crash details into precise, structured bug records that are ready for triage and fix.

Core Features & Use Cases

  • Automatically extract title, reproduction steps, severity, environment (device, OS), and attachments from user descriptions, code snippets, or crash logs.
  • Guide a phase-based workflow from data collection to triage, prioritization, and documentation for consistent issue tracking.
  • Produce ready-to-file bug reports that align with standard bug-tracking workflows and clearly separate Expected vs Actual outcomes.

Quick Start

Provide a user description, a target code path, or a crash log and have it draft a complete, actionable 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 turn vague user descriptions and crash logs into structured bug reports?▼

To create structured bug reports, provide raw user descriptions, code samples, or crash logs. The system extracts the title, reproduction steps, severity, environment, and attachments to output a ready-to-file issue record.

What is the best way to assign severity and priority during bug triage?▼

Bug triage assigns severity and priority by evaluating impact and frequency. The workflow processes collected data to determine the issue's severity and outputs a suggested path and notes for your bug-tracking workflow.

How do I document reproduction steps and separate expected versus actual outcomes?▼

Documenting reproduction steps involves processing user descriptions through a phase-based workflow. The system generates a ready-to-file report that clearly separates expected versus actual outcomes for consistent issue tracking.

Can I use crash logs and code snippets to generate an actionable bug record?▼

Yes, crash logs and code snippets can be used to generate actionable bug records. The system automatically extracts environment details like device and OS from these inputs to produce a complete, structured bug report.

Does the generated bug report align with standard issue tracking workflows?▼

Yes, the generated bug report aligns with standard issue tracking workflows. The output captures essential triage elements and includes a suggested path, referencing a hypothetical build version when needed to ensure workflow compatibility.

Related Skills

Explore More Software Engineering Skills→
SantiagoisperSantiagoisper

ce-report-bug

Create structured GitHub issues for compound-engineering plugin bugs via GitHub CLI.

Community
Intermediate
sunny0826sunny0826
3

issue-triage

Analyze GitHub issue content to classify type, assess completeness, and assign priority.

Community
Intermediate
jupesjupes
2

qa

Facilitates conversational bug reporting and creates durable Beads issues.

Community
Intermediate
BrennonTWilliamsBrennonTWilliams
7

ll-refine-issue

Refine software issue documentation via codebase research and gap analysis.

Community
Intermediate