skills.rest
baphled
baphledCOMMUNITY
Explore all skills by this author →
Website𝕏@baphledGitHub

create-bug

Structure bug reports with reproduction steps, severity, and environment details.

1|Updated Mar 5, 2026
Search Tags:#bug report#software quality#reproducibility#issue creation#defect tracking
One-click install
npx skills add https://github.com/baphled/dotopencode --skill create-bug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-bug
Source: https://github.com/baphled/dotopencode/tree/main/skills/create-bug
Command: npx skills add https://github.com/baphled/dotopencode --skill create-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of reporting bugs by providing a standardized, structured format that ensures all necessary information for diagnosis and resolution is captured upfront.

Core Features & Use Cases

  • Reproducible Bug Reports: Ensures bugs can be reliably reproduced by including clear steps.
  • Severity Classification: Helps prioritize bugs based on their impact (P0-P3).
  • Environment Details: Captures crucial context like versions and OS.
  • Use Case: When a critical feature fails unexpectedly, use this skill to generate a detailed bug report that includes exact steps to reproduce, error messages, and environment specifics, enabling developers to fix it rapidly.

Quick Start

Use the create-bug skill to generate a bug report for a crash when opening an empty timeline.

Frequently Asked Questions about create-bug

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

FAQPage Schema
How do I structure a bug report for fast fixing?▼

To structure a bug report for fast fixing, include clear reproduction steps, expected versus actual behavior, severity classification, and environment details to ensure efficient tracking and resolution.

What should a reproducible bug report include?▼

A reproducible bug report should include exact steps to reproduce the issue, error messages, environment specifics like OS and versions, and a defined severity classification to help developers fix it rapidly.

How do I classify bug severity when creating a GitHub issue?▼

Classify bug severity when creating a GitHub issue by assigning priority levels from P0 to P3 based on the defect's impact, helping teams prioritize tracking and fixing critical software failures efficiently.

Can I use this skill to document defects for any software development workflow?▼

Yes, you can use this skill to document defects for any software development workflow by applying a standardized bug report template that captures environment details and reproduction steps for issue creation.

What is the best way to document software defects for issue tracking?▼

The best way to document software defects for issue tracking is using a standardized format that captures expected versus actual behavior, environment details, and clear reproduction steps to ensure reproducibility and rapid resolution.

Related Skills

Explore More Software Engineering Skills→
Andreicr1Andreicr1

report-bug-ce

Collect bug details and create a GitHub issue for the compound-engineering plugin.

Community
Advanced
baekenoughbaekenough
13

professor-triage

Analyze GitHub issues against the codebase and post prioritized triage comments.

Community
Advanced
chendongqichendongqi
110

testing-test-manager

Coordinate test planning, progress tracking, defect triage, and coverage analysis.

Community
Advanced
CodePhobiiaCodePhobiia
8

bug-report

Create structured bug reports with repro steps and severity classification.

Community
Intermediate